lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <200503101711.j2AHBsuJ017955@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Reverse dns 

On Thu, 10 Mar 2005 09:57:57 CST, Paul Schmehl said:

> I've been looking through the RFCs and I can't find it.  Some folks think 
> reverse dns should be completely disabled.  I know for sure that this will 
> break email, because many mail servers won't talk to a server that doesn't 
> reverse.  Tcpdump also doesn't like hosts that won't reverse.

"tcpdump -n" is your friend. :)

There's no RFC requirement that there be a valid PTR record.  Also, note that
there's *lots* of games that can be played with PTR records if they happen to
be out of a in-addr.arpa zone controlled by the attacker.....
-------------- 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/20050310/818c8d2e/attachment.bin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ