pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpassword strength verification
2+ messages / 2 participants
[nested] [flat]
* password strength verification
@ 2008-12-18 16:26 Rex Mabry <rexmabry@yahoo.com>
0 siblings, 1 reply; 2+ messages in thread
From: Rex Mabry @ 2008-12-18 16:26 UTC (permalink / raw)
To: pgsql-admin
Hi,
If a company requires a password to be a combination of letters, numbers and special characters. Oracle has a profile setting with a password verify function that can be used to specify a function that can do this. Does postgres have a setting or function to verify and enforce a password policy? I am very familiar with pg_hba.conf, but I am looking specifically at passwords.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: password strength verification
@ 2008-12-18 18:04 Chris Browne <cbbrowne@acm.org>
parent: Rex Mabry <rexmabry@yahoo.com>
0 siblings, 0 replies; 2+ messages in thread
From: Chris Browne @ 2008-12-18 18:04 UTC (permalink / raw)
To: pgsql-admin
rexmabry@yahoo.com (Rex Mabry) writes:
> If a company requires a password to be a combination of letters,
> numbers and special characters. Oracle has a profile setting with a
> password verify function that can be used to specify a function
> that can do this. Does postgres have a setting or function to
> verify and enforce a password policy? I am very familiar with
> pg_hba.conf, but I am looking specifically at passwords.
If I were wanting to enforce this, I think I'd do it via PAM.
That is, I would configure PostgreSQL to use the PAM service (METHOD =
"pam", OPTION = name of PAM service), and configure these requirements
into the PAM service.
There are several alternative indirections available:
- LDAP authentication would allow you to manage password policy
in the LDAP instance, quite independent of PostgreSQL.
- krb5 indicates use of Kerberos, which would, again, keep passwords
out of PostgreSQL altogether.
With all of these options being readily available for using
centralized authorization management and policy, I don't see any
particular value in duplicating low level security policy mechanisms
in PostgreSQL.
--
output = ("cbbrowne" "@" "cbbrowne.com")
http://linuxdatabases.info/info/postgresql.html
"Well, I wish you'd just tell me rather than trying to engage my
enthusiasm, because I haven't got one." -- Marvin the Paranoid Android
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2008-12-18 18:04 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-12-18 16:26 password strength verification Rex Mabry <rexmabry@yahoo.com>
2008-12-18 18:04 ` Chris Browne <cbbrowne@acm.org>
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