It should be shipped with AES encryption as the default with DES and this exit
as options. There should, of course, be large warnings about what
defaults/options may be incompatible with prior releases of the product.
It would be nice if the product could sense if the current settings are
incompatible with the current database and provide some conversion mechanism to
bring the old database up to the new settings.
/Tom Kern
--- Alan Altmark <[EMAIL PROTECTED]> 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
>
____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play
Sims Stories at Yahoo! Games.
http://sims.yahoo.com/
