🚀 go-pugleaf

In <71269183717599@juju.mcs.anl.gov> nickless@juju.mcs.anl.gov (Bill Nickless):
>Currently the file looks like this:
>-rw-r--r--  1 nickless 107137306 Jul 12 20:40 bigdict.sorted
>You then do a binary search against this.  The search probe scans for the 
>first full word near the computed byte address.  Once you narrow it down 
>to about 100 bytes then a simple linear search happens.

Knowing where the binary search finished would tell a cracker the first
few characters of the actual password, greatly reducing the search space.

If they can snoop NFS packets off the ethernet they can learn this
directly.  If they can login to either the NFS server, or the client
where the password change took place, it might also be possible to
figure it out by the doing timed reads on the bigdict.sorted file
and intuiting which reads were satified from the buffer cache and
which required physical I/O.
-- 
Jim Prescott	jgp@moscom.com		{rit,tropix,ur-valhalla}!moscom!jgp