From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
---|---|
To: | "'D'Arcy J(dot)M(dot) Cain'" <darcy(at)druid(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Password policy |
Date: | 2008-01-16 16:17:39 |
Message-ID: | 1A6E6D554222284AB25ABE3229A92762715451@nrtexcus702.int.asurion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: D'Arcy J.M. Cain [mailto:darcy(at)druid(dot)net]
> Sent: Wednesday, January 16, 2008 9:39 AM
> To: Andrew Dunstan
> Cc: Roberts, Jon; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Password policy
>
> On Wed, 16 Jan 2008 08:32:12 -0500
> Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> > >> I need to set a basic password policy for accounts but I don't see
> any
> > > Look at my chkpass type in contrib. There is a function to verify the
> > > password. It is just a placeholder now but you can modify it to do
> all
> > > your checking.
> >
> > I assumed he was asking about Postgres level passwords rather than
> > passwords maintained by an application. chkpass is only for the latter.
>
> Could be. I saw "accounts" and thought Unix shell or ISP accounts.
>
I was referring to PostgreSQL accounts.
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-16 16:22:57 | Re: Some ideas about Vacuum |
Previous Message | Florian G. Pflug | 2008-01-16 16:07:04 | Re: Transaction Snapshot Cloning |