Re: 11g password complexity
- From: kathryn axelrod <kat.axe@xxxxxxxxx>
- To: jkstill@xxxxxxxxx
- Date: Tue, 27 Apr 2010 14:23:39 -0700
In the past I've had to modify passwords or scripts due to issues
encountered with punctuation in the passwords. But that just means that we
don't use those particular characters any more - not that we got rid of the
punctuation requirement altogether.
I suppose this is where my curiosity comes from - I would ~think~ that if
this were the reason for the change, that Oracle would simply reduce the
characters available in the script's array to the innocuous ones as opposed
to eliminating the requirement entirely. Perhaps I'm missing something
though?.
On Tue, Apr 27, 2010 at 2:13 PM, Jared Still <jkstill@xxxxxxxxx> wrote:
>
> On Tue, Apr 27, 2010 at 1:02 PM, <lyallbarbour@xxxxxxxxxxxxxxx> wrote:
>
>> We had a problem with... the @ symbol, i think. One of the punctuations
>> for passwords when a user would fire off an Oracle Report. Maybe that is
>> one of the reasons...
>>
>>
> Ditto that. Do not use '@' in an oracle password.
>
> We do use a number of other punctuation characters though.
>
> #!$%^()[]{} and even & and * work, though I tend to avoid & and *
> probably would avoid '.' as well, though I've not tried it.
>
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
> Oracle Blog: http://jkstill.blogspot.com
> Home Page: http://jaredstill.com
>
>
Other related posts:
