Content-Type: text/plain;
 charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Passwords in DBA_USERS (Oracle 12c)
From: Ryan January <rjanuary@gmail.com>
In-Reply-To: <577DA534.2090905@gmail.com>
Date: Wed, 6 Jul 2016 19:54:31 -0500
Cc: Ricardo Arnoud <ricardoskn@gmail.com>,
 oracle-l <oracle-l@freelists.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <35D0FDF1-E93C-42F8-98FA-299DC4F03FC4@gmail.com>
References: <577D96E8.60502@gmail.com> <CAC540oiLsoSZ+26yqv0ecmFq8P__4+NbGQUPjQgLqGqjZPkEGQ@mail.gmail.com> <577DA534.2090905@gmail.com>
To: gogala.mladen@gmail.com
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: rjanuary@gmail.com


As far as I'm aware, it was done to support case sensitive passwords. =20
If it wasn't officially documented by Oracle, it's been unofficially documen=
ted for years by the commit it at large.

> On Jul 6, 2016, at 7:41 PM, Mladen Gogala <gogala.mladen@gmail.com> wrote:=

>=20
>> On 07/06/2016 07:50 PM, Ricardo Arnoud wrote:
>> Try the following for 12c:
>>=20
>> select 'ALTER USER '||name||' identified by values '||CHR(39)||spare4||';=
'||password||CHR(39)||';'
>> from user$ where name in ('SCOTT');
>=20
> Hi Ricardo,
> I know that SPARE4 is SHA version of the password hash, but my point was m=
ore to clarify why was it done, and even more importantly, why wasn't such a=
n important change documented? It is also possible to extract the hash using=
 DBMS_METADATA.GET_DDL. I have solved my original problem, that's not the po=
int.
>=20
> Regards
>=20
>=20
> --=20
> Mladen Gogala
> Oracle DBA
> Tel: (347) 321-1217
>=20
> --
> http://www.freelists.org/webpage/oracle-l
>=20
>=20
--
http://www.freelists.org/webpage/oracle-l