Patches coming today for DNS vulnerability


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Patches coming today for DNS vulnerability
# 1  
Old 07-08-2008
Patches coming today for DNS vulnerability

Tue, 08 Jul 2008 19:05:22 GMT
Whether you're running Linux, Windows, Cisco, Sun, or other DNS servers, you are at risk from a newly discovered vulnerability. So says Dan Kaminsky, head of penetration testing research at IO Active, who accidently discovered the DNS "design flaw" earlier this year.


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. AIX

List of Installed patches for AIX from given set of patches

I need to find out list of installed patches from given list of patches. I have tried using instfix -f <File containing list of patches> -i -c But I was not able to understand the output of this command. It was like below. bos.perf.tools: :0.0.0.0:?: bos.rte.libc: :0.0.0.0:?: ... (4 Replies)
Discussion started by: Saurabh Agrawal
4 Replies

2. Shell Programming and Scripting

meaning of today=${1:-${today}}

what does today=${1:-${today}} mean??? I saw a script which has these two lines: today=`date '+%y%m%d'` today=${1:-${today}} but both gives the same value for $today user:/export/home/user>today=`date '+%y%m%d'` user:/export/home/user>echo $today 120326... (2 Replies)
Discussion started by: Vidhyaprakash
2 Replies

3. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies
Login or Register to Ask a Question
Net::DNS::Resolver::Recurse(3)				User Contributed Perl Documentation			    Net::DNS::Resolver::Recurse(3)

NAME
Net::DNS::Resolver::Recurse - Perform recursive dns lookups SYNOPSIS
use Net::DNS::Resolver::Recurse; my $res = Net::DNS::Resolver::Recurse->new; DESCRIPTION
This module is a sub class of Net::DNS::Resolver. So the methods for Net::DNS::Resolver still work for this module as well. There are just a couple methods added: hints Initialize the hint servers. Recursive queries need a starting name server to work off of. This method takes a list of IP addresses to use as the starting servers. These name servers should be authoritative for the root (.) zone. $res->hints(@ips); If no hints are passed, the default nameserver is asked for the hints. Normally these IPs can be obtained from the following location: ftp://ftp.internic.net/domain/named.root recursion_callback This method is takes a code reference, which is then invoked each time a packet is received during the recursive lookup. For example to emulate dig's "+trace" function: $res->recursion_callback(sub { my $packet = shift; $_->print for $packet->additional; printf(";; Received %d bytes from %s ", $packet->answersize, $packet->answerfrom ); }); query_dorecursion This method is much like the normal query() method except it disables the recurse flag in the packet and explicitly performs the recursion. $packet = $res->query_dorecursion( "www.netscape.com.", "A"); IPv6 transport If the appropriate IPv6 libraries are installed the recursive resolver will randomly choose between IPv6 and IPv4 addresses of the nameservers it encounters during recursion. If you want to force IPv4 transport use the force_v4() method. Also see the IPv6 transport notes in the Net::DNS::Resolver documentation. AUTHOR
Rob Brown, bbb@cpan.org SEE ALSO
Net::DNS::Resolver, COPYRIGHT
Copyright (c) 2002, Rob Brown. All rights reserved. Portions Copyright (c) 2005, Olaf M Kolkman. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. $Id: Recurse.pm 740 2008-12-17 23:20:53Z olaf $ perl v5.12.1 2009-12-30 Net::DNS::Resolver::Recurse(3)