Re: password complexity -- implementing security changes

From: Jared Still <jkstill_at_gmail.com>
Date: Fri, 3 Mar 2006 17:41:10 -0800
Message-ID: <bf46380603031741h53d51262mbd863ea43f3a4fec@mail.gmail.com>

On 3/3/06, MARK BRINSMEAD <mark.brinsmead_at_shaw.ca> wrote:

> Okay, so why is *that* a problem? After all,
> last time I checked, Oracle database passwords
> were case-insensitive anyway...

Because the poster claimed to be using verify_function to enforce case in passwords. You can't do it.

If your password policy requires mixed case (as ours does) you will need to amend the policy for Oracle (as we did)

Special characters, on the other hand, *can* be a
> problem. I seem to recall even SQL*Plus giving
> me considerable grief with a password that
> contained "/" characters... No wait; it was a
> Pro*C application.

... and determining just what the problem is can be rather time consuming.

--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Mar 03 2006 - 19:41:10 CST