Re: drupal.org MySQL database issues

From: Joshua Kramer <josh(at)globalherald(dot)net>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: drupal.org MySQL database issues
Date: 2007-05-21 17:26:20
Message-ID: Pine.LNX.4.64.0705211323020.10694@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy


On Sun, 20 May 2007, Chris Browne wrote:

> Making a selection of mechanisms configurable seems entirely
> reasonable to me.

But, whilst creating these systems, we must keep in mind security.
Instead of replacing the auth routines, how about:

1. Keep the auth routines currently present in PG, so that as a DB admin I
*can* restrict DB's via file only as I do now, and

2. To support those who want LDAP or table-based auth, add a setting to
pg_hba.conf so that a second code-path can be activated on a per-db basis.

I view MySQL's table-based auth mechanisms as a bug, not a feature.

Cheers,
-J

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Andrew Sullivan 2007-05-22 15:45:17 Re: drupal.org MySQL database issues
Previous Message David Fetter 2007-05-21 14:57:57 Re: drupal.org MySQL database issues