Re: (PM) SECURITY PROBLEM.

Jason Marshall (marshalj@spots.ab.ca)
Tue, 7 Jul 1998 23:33:47 -0600 (MDT)

> This has been mentioned before in the list. It seems to come up every
> now and then. Somewhere in the docs or the release note or web-site it
> used to be mentioned to always reset the console or the next person to
> telnet in *may* see the debug output. I guess it attaches the debug
> output to one of the 4 telnet sessions and if you hit the one that has
> the console attached to it, it starts spewing at you.
>
> At any rate, I know Livingston knows about this, as they have warned about
> it before.

Well I'll be damned. I just telnetted to one of our PM3's, set console,
set debug 0x51, and logged out. Then I telnetted to the PM3 in 4
different xterms, and sat at the login prompt. After a couple seconds,
debug information started flying past! This has GOT to be a bug...

Luckily, I don't do much debugging on our PM3s because they work so well
*8-)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| Jason Marshall, marshalj@spots.ab.ca. Spots InterConnect, Inc. Calgary, AB |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>