That's almost the question. What should be the shipment default? DES
encryption or the prior hash format? There is no question that it
should be able to support the previous type of encryption. My
contention is that most shops use DES encryption and the default should
be DES. I certainly think that both forms should be supported as long
as both are used. I was really trying to find out if a majority use DES
or the previous form.
Jim
Alan Altmark wrote:
On Friday, 05/25/2007 at 01:20 AST, Jim Bohnsack <[EMAIL PROTECTED]>
wrote:
I'd be interested in a show of hands to find out if others prefer to and
do roll your own for database password encryption vs. using RACF's DES
code. I told the RACF developer that I'd let him know what I found.
I think your question is: Should RACF be shipped with DES encryption
enabled by default, or should it be compatible with prior releases of the
RACF database? The exit is telling RACF to use the hash format instead of
built-in DES encryption (the default if the exit is not provided at all).
Alan Altmark
z/VM Development
IBM Endicott
--
Jim Bohnsack
Cornell University
(607) 255-1760
[EMAIL PROTECTED]
