From: Adam Lang <aalang@rutgersinsurance.com>
To: pgsql-php@postgresql.org
Subject: Re: Web Security
Date: Tue, 27 Feb 2001 09:37:43 -0500
Message-ID: <00e201c0a0ca$d7e7bb20$330a0a0a@rutgersinsurance.com> (raw)
References: <200102271405.OAA16033@student.cs.ucc.ie>
Like you said, have separate users with separate security.
For the people that are only allowed to look at info, implement views on the
postgresql database that only allow basic select statements.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Paul Joseph McGee" <mcgee@student.cs.ucc.ie>
To: <pgsql-php@postgresql.org>
Sent: Tuesday, February 27, 2001 9:05 AM
Subject: [PHP] Web Security
> Hi everybody,
> I am trying to implement a website where users may login and view
> available properties. Basically it is an online auctioneering site which
> is my final year project. I want to be able as SysAdmin to log in
> myself
> and modify, add properties, upload images etc. At the moment I am toying
> with letting
> both users and SysAdmin log in from the same authentication window. The
> properties are all saved in a PostgreSQL database on my machine here. I
> have created a user <webadmin> who has insert, update, select and delete
> priveleges
> on all tables in my database. This user is unable to create databases or
> users. When the SysAdmin logs in he will have a page where he can modify
> houses etc, while when an ordinary user logs in he will have the basic
> window where he can search for houses. At the moment I have it such that
> both users and SysAdmin when connected are connected as webadmin. I dont
> think this is a very secure method but its all i can think of at the
> moment. I'm also not sure how to kep the SysAdmin's page secure from
> everybody else. At the moment all my pages are in a
> /usr/local/apache/htdocs/project/ directory. Does anybody have an idea how
> i could make this implementation more secure and functional.
> Thanks,
> Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: aalang@rutgersinsurance.com
Subject: Re: Web Security
In-Reply-To: <00e201c0a0ca$d7e7bb20$330a0a0a@rutgersinsurance.com>
References: <200102271405.OAA16033@student.cs.ucc.ie> <00e201c0a0ca$d7e7bb20$330a0a0a@rutgersinsurance.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox