Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




bugtraq logo Bugtraq mailing list archives

Re: glibc resolver weakness
From: Valdis.Kletnieks () VT EDU (Valdis.Kletnieks () VT EDU)
Date: Wed, 3 May 2000 15:58:48 -0400


On Wed, 03 May 2000 03:40:46 +0200, antirez <antirez () LINUXCARE COM>  said:
Hi all,

this is from glibc 2.1.3 resolver source code:

u_int
res_randomid()
{
        struct timeval now;

        __gettimeofday(&now, NULL);
        return (0xffff & (now.tv_sec ^ now.tv_usec ^ __getpid()));
}

The exact same code as in the BIND 8.2.2-p5 src/lib/resolv/res_init.c

I've *NOT* evaluated if there's an actual problem here, but if there is,
it's probably in *every* BIND-derived resolver...

--
                                Valdis Kletnieks
                                Operating Systems Analyst
                                Virginia Tech



  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]