OS400 has a windows compatible hash algorythm....
<snip from a COMMON presentation I found>
Starting with V5R1, all passwords are also encrypted using SHA-1. If the value of "0" or "1" is being used, the DES
encryption is being used to signon as was done before. If a value of "2" or "3" is selected, an SHA-1 generated
password token is used to signon.
To enable migration, the DES encryption value for level "0" to "2" is kept on the system for each user ID and
password. At level "0" to "2", newly created user IDs and passwords will continue to have both a DES and a SHA-1
encrypted version of their password. For level "3", only the SHA-1 version is created, stored and used.
The clear text password will be encrypted producing a 20-byte password token (also referred to as 'passphrase') as
follows:
Conversion of the clear text password to Unicode CCSID 13488
Conversion of the clear text user ID to Unicode CCSID 13488
Use of SHA-1 to hash the ID and password producing the 20-byte token.
<end>
Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Walden H. Leverich
Sent: Friday, October 19, 2007 4:48 PM
To: Midrange Systems Technical Discussion
Subject: RE: Writing to a Windows server instead of to the IFS
using the userid/password you're signed into i5/OS under
That's always disturbed me. If passwords are stored in a one-way hash on
the 400, how does the 400 respond to the authentication challenge?
-Walden
midrange.com
