Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: password complexity -- implementing security changes

RE: password complexity -- implementing security changes

From: Smith, Steven K - MSHA <Smith.Steven_at_DOL.GOV>
Date: Fri, 3 Mar 2006 13:26:01 -0700
Message-ID: <A49A36C009B8884C9246B36A0DA7923F01348978@msha-lak-exmb01.msha.dir.labor.gov>


Try an Oracle password with a '@' in it. That one took awhile to figure out the first time I saw it.

Steve Smith
Envision Technology Partners / MSHA MSIS Team Desk: 303-231-5499

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of MARK BRINSMEAD Sent: Friday, March 03, 2006 1:22 PM
To: jkstill_at_gmail.com
Cc: venu_potluri_at_ml.com; rjamya_at_gmail.com; wbfergus_at_usgs.gov; oracle-l_at_freelists.org
Subject: Re: password complexity -- implementing security changes

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

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.

>
>
> One thing the verify_function cannot do is enforce upper or lower
> case.Try it, case doesn't matter.
>
> While on the subject, be careful with those special characters.
>
> Some applications do not like them.
>
> Net Backup for instance will not work if there is a @ or ^ in the
> passwordfor the account used to do backups.
>
>
>
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
>

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

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Mar 03 2006 - 14:26:01 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US