Priority: normal
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
Subject: RE: password complexity -- implementing security changes
Date: Fri, 3 Mar 2006 13:47:16 -0700
Message-ID: <7209E76DACFED9469D4F5169F9880C7A9CC1@mail01bldr.arraybp.com>
Thread-Topic: password complexity -- implementing security changes
thread-index: AcY/Aqfg2nCkepmIRdi1/9DdWZMTQwAAHZ2Q
From: "Reidy, Ron" <Ron.Reidy@arraybiopharma.com>
To: <paul.baumgartel@credit-suisse.com>, <oracle-l@freelists.org>
Sender: oracle-l-bounce@freelists.org
Errors-To: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: Ron.Reidy@arraybiopharma.com

While these password rules might be the "official rules", I believe they
are of the legacy variety.  I have passwords that:

1.  Do not start with an alpha character ([az])
2.  That contain the ^%!=+?<>{}[]|\ characters

None of these cause issues in our apps or using any Oracle client tools
(both Oracle developed and 3rd party).

-----Original Message-----
From: oracle-l-bounce@freelists.org
[mailto:oracle-l-bounce@freelists.org] On Behalf Of Baumgartel, Paul
Sent: Friday, March 03, 2006 1:38 PM
To: oracle-l@freelists.org
Subject: RE: password complexity -- implementing security changes


An Oracle password has the following rules: 
A password must begin with an alphabetic character. 
Passwords can contain only alphanumeric characters and the underscore
(_), dollar sign ($), and pound sign (#). 

So your @s, your /s, and your ^s are problematic from the get-go.

Paul Baumgartel
paul.baumgartel@credit-suisse.com
212.538.1143


-----Original Message-----
From: oracle-l-bounce@freelists.org
[mailto:oracle-l-bounce@freelists.org]On Behalf Of MARK BRINSMEAD
Sent: Friday, March 03, 2006 3:22 PM
To: jkstill@gmail.com
Cc: venu_potluri@ml.com; rjamya@gmail.com; wbfergus@usgs.gov;
oracle-l@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.


----- Original Message -----
From: Jared Still <jkstill@gmail.com>
Date: Friday, March 3, 2006 12:30 pm
Subject: Re: password complexity -- implementing security changes

> 
> 
> 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


========================================================================
======
Please access the attached hyperlink for an important electronic
communications disclaimer: 

http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
========================================================================
======

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


This electronic message transmission is a PRIVATE communication which contains
information which may be confidential or privileged. The information is intended 
to be for the use of the individual or entity named above. If you are not the 
intended recipient, please be aware that any disclosure, copying, distribution 
or use of the contents of this information is prohibited. Please notify the
sender  of the delivery error by replying to this message, or notify us by
telephone (877-633-2436, ext. 0), and then delete it from your system.

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