Thursday, August 26, 2004


aircrack 1.4. aircrack is an 802.11 WEP cracking program that can recover a 40-bit or 104-bit WEP key once enough encrypted packets have been gathered. It implements the standard FMS attack along with some optimizations, thus making the attack much faster compared to other WEP cracking tools. [freshmeat.net]

So I don't I even bother with WEP.  Just allow only registered NICs and don't pass overly sensitive over the air:-)


9:59:33 AM    comment []  trackback []  

A New Home for Boley. Paul L. Boley Law Library BoleyBlogs! is back, and it is darn proud of the new home and new look of the Lewis & Clark Law School Library's website. Check it out at http://lawlib.lclark.edu and, please, let us know what... [BoleyBlogs!]

New website for L&C Law Library is nice.  It includes an aggregator page, which is a very good thing.


9:53:31 AM    comment []  trackback []  

PHPlist: Not your everyday Mailman. Like many (if not most) open source developers, I use Mailman, the GNU mailing list manager, for all of my newsletter requirements. Recently, however, I began playing with a different one-way announcement-type newsletter mailer. It's called PHPlist, and as you might guess, in contrast to Mailman, it's not Python powered. Beyond the language difference, it adds a number of useful default features, including email from RSS feeds and sophisticated user management that really extends the power of an announcement-based mailing list. [NewsForge]
8:30:56 AM    comment []  trackback []  
Microsoft addresses NAT conflict introduced by SP2 - News - ZDNet
Microsoft addresses NAT conflict introduced by SP2 - News - ZDNet "Based on tests conducted by ZDNet, one SP2-injected change in Windows XP that could interfere with plans to roll out SP2 appears to involve a loss of network connectivity for workstations that use Microsoft’s L2TP-based virtual private networking (VPN) client to connect to servers that are connected to NAT-based networks (explained below). Based on an SP2 design decision, Microsoft refers to the anomaly as an expected change to the default behavior of Windows XP, which, prior to the update, allowed for L2TP-based connectivity to NAT-based servers. "
8:18:02 AM    comment []  trackback []