RE: Automatic Signon/Telnet: How can the 5250 client differentiate between V5R1 and Pre-V5R1 Releases at signon time?

Thanks Patrick,

I do send a seed request of 28 bytes at the beginning, but the seed reply
does not contain any QPWDLVL bit. Can you please give a sample showing how
identify the QPWDLVL bit or any reference that can help here?

I am using the following 28 bytes Host Seed Reply structure:
{Length(4)|Header ID(2)|Server ID(2)|CS Instance(4)|Correlatio
ID(4)|Template Length(2)|Reply ID(2)|Primary RC(2)|Secondary RC(2)|Host
Seed(8)}

Thanks
N.Khoury

-----Original Message-----
From: midrange-l-bounces+nageeb=khoury.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+nageeb=khoury.com@xxxxxxxxxxxx] On Behalf Of
Patrick Botz
Sent: Thursday, February 10, 2005 1:51 AM
To: Midrange Systems Technical Discussion
Subject: Re: Automatic Signon/Telnet: How can the 5250 client differentiate
between V5R1 and Pre-V5R1 Releases at signon time?

The TN5250e protocol lacks any way for the client to know when to send SHA
or DES.    This is because the password substitute protocol you are
referring to was invented for use only with Client Access/iSeries Access
bypass-signon.  Since that client requires a license, it's already made
other connections/flows to the iSeries and discovered the host password
level along the way.


The current solution/hacks are:
- make a seperate connection to any iSeries Access server and send the seed
flow (28 bytes), the returning host seed flow (28 bytes) also contains the
QPWDLVL bit.   Then you can cache this or discover it each time.
- require all iSeries to move up to SHA
- use kerberos instead

Patrick Botz

-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.