[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <200405111705.i4BH5s5Y028556@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Victory day - Sasser surrenders
On Tue, 11 May 2004 15:34:19 BST, Rob Clark <rob@...er-worx.co.uk> said:
>
> 193.x.x.x isnt internal,,, is it?
> > > I'd remove something from the mailer:
> > > Received: from [192.168.195.2] ([193.7.145.26])
Of course, that line was added by the system that received the mail *FROM*
193.7.145.26.. About all you can discover from it is that said box is
probably NAT'ed, and gave an EHLO with the 192.168 address on it.
For Sendmail, you can fix that information leakage by adding
CLIENT_OPTIONS(`Family=inet, Address=0.0.0.0, M=h')
to your .mc file (the M=h causes it to use the interface name rather
than the host hame on the ELHO).
Oh, and that neither address has a workable in-addr.arpa PTR.. ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040511/769b8305/attachment.bin
Powered by blists - more mailing lists