You can also propose to everyone who want to verify the integrity of its system to check that himself. A script like chkrootkit which search for the signature of a past ssh (or other) attack. A simple reference in the doc of ssh could alarm lots of people. cron ta run it periodically, and don't bother to find a contact address.
On Thu, 23 Dec 2004 13:31:27 -0800, Karsten M. Self <kmself@ix.netcom.com> wrote: > > Attacking people's boxen running ssh seems to be a popular passtime at > > the moment, it would be good to have a way to fight back against this > > trend, rather than just protecting our own machines. > > > > Maybe there's some good reason NOT to contact people, I can't think > > why. Might not want to use your canonical email address though! -- Marc Demlenne GPG : 768FA483 (http://pgp.mit.edu) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
