Re: Call for LAMP Standardization -- Installations/User-Group Admin

Google Mike wrote:

> <snip>
>> 3. The template app comes with either MySQL and equivalent PostgreSQL
>> tables for users, groups, and members (group memberships). It contains
>> the most basic things one would think of using. It also uses shadow
>> passwords, rather than real passwords, in the users table.
>
> Done. Though actually we use db security, not *nix security....
>
> ...
>> 4. The install creates a new local Linux account that will be used by
>> the PHP pages to authenticate to the database, along with password. It
>> prompts you for the password and recommends that you change this every
>> so many days.
>
> Again, security is tied to a database, at least in my world.
> - Kenneth Downs
> </snip>
>
> Uh, yeah, you are right. I do prefer DB security -- no sense giving
> people an account to login to the server that way. So the users and
> groups thing -- that's in the tables in the db.
>
> However, that aside, the PHP pages have to have something to pass to
> pg_connect(), and often big corporations don't like the db account of
> "root" or "postgres" to use that. So, instead, one has to create an
> account (often this account is named something similar to the app name)
> in the database.

Which is as it should be. The database is full of groups that have certain
security rights, and you make a person real by creating their account and
putting them into their groups.

The anti-technique of having all connections going through a bogus account
leads to no end of trouble, not the least of which is the complete lack of
ability to use real server-side security, and the horrible dangers
associated with the fact that this bogus account must carry the highest
possible priveleges.

--
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@(Sec)ure(Dat)a(.com)
.

Relevant Pages

  • Re: Changing security authentication type.
    ... i'm thinking that yes in time the sa account will ... Create one or more logins for the applications. ... for each database. ... , you really have no security for your ...
    (microsoft.public.sqlserver.security)
  • [NEWS] UTStarcom B-NAS 1000 and B-RAS 1000 Security Flaw
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... with known passwords. ... Issanni 1000) One account is approximately equal ... Management user with limited write privileges ...
    (Securiteam)
  • Re: How secure is a secured database?
    ... I'm pretty confident that I've covered the guidelines in the Security setup ... While the main database will have the sensitive cost issues - i.e. their ... the plaintext passwords from a workgroup file. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Windows service
    ... if you know all of this why you recommend to Rotsey not to use Domain Security? ... It's easily cracked, doesn't have any metering on it to prevent brute force attacks, transmits the credentials to the database in plain-text, and doesn't integrate at all into the standard security infrastructure already being used by the organization. ... There's no default monitoring of the invalid password attempts, no automatic account lock-out, etc. There's a ton of documentation on this found on the web. ... It's one less set of passwords to remember, less configuration in the long run, fewer plain-text passwords floating around in email & config files. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Machine.Config -- ProcessModel vs Identity Impersonation
    ... in the case of wanting to access a network share or database (integrated ... security) which would be better or expose the least in security ... > authenticated in IIS or the anonymous account if none is authorized. ... >>processmodel section vs using one in impersonation in the machine.config ...
    (microsoft.public.dotnet.framework.aspnet)