RE: setsppfp bug

["Bale, Dan" <DBale@xxxxxxxx>]

So, you just have to keep "sniffing" in a loop?  

BTW, I tried signing on in another session and immediately switched to
another session and called the program, probably within 3 seconds of signing
on.  Got the same results.

Waited a few minutes...  Holy Cow!  Got a good hit!  This oughtta make our
AS/400 sysadmin real happy!

Does only the user's first signon register change to the ODP?  I tried the
test again mentioned above and still not seeing my userID and PW, just the
same person that popped up last.  (I'll test this when I have a break and
can sign off all four of my sessions.)

What kind of activity changes the ODP?  Is there enough activity that the
ODP would likely be changed on a second-by-second basis?  Would you have
expected my test mentioned above would have sniffed my user ID & password?

Has IBM responded to this bug?

- Dan Bale

> -----Original Message-----
> From: Gene_Gaunt/ReviewWorks@reviewworks.com
> [SMTP:Gene_Gaunt/ReviewWorks@reviewworks.com]
> Sent: Thursday, June 08, 2000 12:07 PM
> To:   MI400@midrange.com
> Subject:      RE: setsppfp bug
> 
> Dan, what you observed is the output buffer that overlays the input
> buffer.
> The first two output byte values are DDS indicators on the sign-on screen.
> The sniff program retrieves whatever sits in the ODP last: output or
> input.
+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---