× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2005

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.