full-disclosure - Strange ldap Behavior.

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]

From: Webmaster at PhatOrWhack.com (Steele)
Subject: Strange ldap Behavior.

Don't have too much experience with ldap or how you're using it, but my
money would be on prisoner.iana.org
Check google for more info

p34ce
Steele

-----Original Message-----
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com]On Behalf Of Soderland, Craig
Sent: Tuesday, May 18, 2004 9:16 AM
To: full-disclosure@...ts.netsys.com
Subject: [Full-Disclosure] Strange ldap Behavior.

Guys,

 I did a snoop from our tech sandbox (xxxxxx) to port 389 using the
 following command: 'snoop -v port 389' (without the quotes). The attached
 file shows a segment of the results. Notice the line:

      ETHER:  Destination = 0:0:5e:0:1:1, U.S. Department of Defense
 (IANA)

 Why should a connection be made to US Dept. of Defense? Any Ideas?