full-disclosure - Re: Links to Google's cache of 626 FrSIRT exploits

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: <dvpnpr$d6h$1@sea.gmane.org>
Date: Tue Mar 21 20:31:17 2006
From: davek_throwaway at hotmail.com (Dave Korn)
Subject: Re: Links to Google's cache of 626 FrSIRT exploits

layne@...enot.com wrote:
> So you never recursively sucked FrSIRT.com before the public exploits
> section was "definitively closed" well we're in luck (at least for a
> little while) because Google did.
>
> This page links to Google's cache of 626 FrSIRT exploits
>
> http://www.elsenot.com/frsirt-google.html

  If you want to fetch them with wget, you'll need to supply a plausible 
user-agent using the -U option on the command line.  Without that, google 
just returns a "403 Forbidden".  I found the following technique worked:

wget 'http://www.elsenot.com/frsirt-google.html'
grep -o 'href="[^"]*"' frsirt-google.html | cut -d '"' -f 2 > list.txt
wget -i list.txt -U 'User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; 
en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6'

although IIRC you could also just pipe the output from grep | cut straight 
into wget, should you want to save yourself the temporary listing file.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....