[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <013301c37bd3$4c04e150$531efea9@stickslinger>
From: nodialtone at comcast.net (Byron Copeland)
Subject: new ssh exploit?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Don't know of any myself, but you can set up sshd to listen on port 80 as well. Then ssh or sftp to your box all you wish. You think they'll block port 80? Doubt it. :)
- -b
- -- "I always wonder why people choose to support MS and then complain about all of these issues that are known in advance."
> -----Original Message-----
> From: full-disclosure-admin@...ts.netsys.com [mailto:full-disclosure-
> admin@...ts.netsys.com] On Behalf Of christopher neitzert
> Sent: Monday, September 15, 2003 12:03 PM
> To: full-disclosure@...ts.netsys.com
> Subject: [Full-Disclosure] new ssh exploit?
>
>
> Does anyone know of or have source related to a new, and unpublished ssh
> exploit? An ISP I work with has filtered all SSH connections due to
> several root level incidents involving ssh. Any information is
> appreciated.
>
>
>
>
>
> --
> Christopher Neitzert - GPG Key ID: 7DCC491B
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0
iQA/AwUBP2Y0AGHZJr/4PEW4EQJOHACgzLYRew5Pn5U+ZW/gjRI0yiH4aW0AoMSF
qnRN5TZrNEZtlWCZdPae6H8D
=w6kk
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists