http://keir.net/index.htmlHot News!en2012-02-23T11:30:27-05:00 hourly 1 2000-01-01T12:00+00:00 Sun, 26 Feb 2012 19:11:21 -0500Blog2012-02-23T11:30:27-05:00http://keir.net/blog/files/YouPorn%20Passwords.html#unique-entry-id-61http://keir.net/blog/files/YouPorn%20Passwords.html#unique-entry-id-61revealed after a third-party chat service "failed to take the appropriate precautions in securing its user data”. According to various reports, it resulted in an estimated 1 million user names, email addresses and plain-text passwords being exposed, much to the embarrassment of those individuals I’m sure. My tests saw closer to 2 million unique usernames extracted from the files so I’m not sure why the discrepancy.

Since the data is now effectively in the public domain, I did a quick analysis of the passwords. While some may be attributed to the nature of the content of the aforementioned site, others are the usual suspects, with “123456” taking top honors by a large margin.

Here are the top 50.

]]>Blog2012-02-07T12:03:36-05:00http://keir.net/blog/files/3e0cc1cea0320df5085f06e185a6da1b-60.html#unique-entry-id-60http://keir.net/blog/files/3e0cc1cea0320df5085f06e185a6da1b-60.html#unique-entry-id-60
I had seen KB articles and patches available for WIN2K8R2 that allegedly fixed some latency issues around UDP processing, but we were at SP1 and this was already in place. Regardless, the code that was responsible for sending and receiving the UDP packets on the network was written to use WinPcap, the low level packet capture driver for Windows, and thus should not have suffered from any (comparatively) higher-level changes made in the TCP/IP stack between operating systems.

All manner of extensive tests were run to try to nail down why the scans took so much longer on 2008 R2.

To cut a very long story short, the issue was with the network card driver.

Now usually when I investigate networking problems like this, the very first thing I do is check the NIC settings to make sure they are all correct. Usually the NIC should be in "auto-configure" or "auto-detect" mode and operating in full-duplex. Indeed I had briefly initially looked at both system's NIC properties and both reported to be running at 1 Gbps full-duplex. Nothing to see here. Move on. About the only difference in this area was that the 2K3 box was using older Intel PROSet drivers. Surely nothing major had changed or been fixed since those were released though, right?

Fast forward a number of agonizing days of further debugging and instead of trying to find out what's wrong in the application code, I attempt to see if the problem can be reproduced and isolated with something that does not involve our code at all. Enter the wonderful tool Iperf.

Using Iperf in UDP mode it quickly became apparent something was wrong. Throughput tests from the 2K3 system were half that of the WIN2K8R2 box when tested against the same remote Iperf server. Not just roughly half, but almost exactly half! That's too much of a coincidence.

So what could account for half the throughput? Well, if the NIC was not really operating in full-duplex mode and instead was running in half-duplex, that would be half the bandwidth.

I switched both NICs into 100 Mbps full-duplex mode (curiously the configuration properties of the WIN2K3 NIC did not offer a manual selection for 1 Gbps full-duplex despite the summary claiming it was already running that way) and re-ran the Iperf tests. Amazingly both systems now produced exactly the same throughput!

A slew of application tests were launched again with the new manual NIC settings and the problem was gone. Both systems finished their large UDP scans in consistently similar times.

The NIC properties were lying. It wasn't running full-duplex on the WIN2K3 system.

Problem solved.

One last mystery though. How can increased bandwidth (on the WIN2K8R2 box running 1 Gbps full-duplex versus WIN2K3 running 1 Gbps half-duplex) result in a large UDP scan that runs slower?

To explain this I have to explain how UDP scanning works against typical modern targets.

Most modern operating systems restrict the rate at which they inform the sender if a UDP port is closed (see RFC 1812 and others). They will, for example, only respond once every second with a "closed" ICMP Destination Port Unreachable message regardless of however many probes we've sent that target. Any ports that we've sent probes to that we don't get an explicit "closed" (or "open" for that matter) response from we have to wait for a timeout period in case the packet is slow to arrive.

So imagine we send 100 UDP probes and it takes us 10 seconds to do that. This would represent the 2K3 system running in half-duplex. During that time we may receive 10 "closed" replies (at a rate of 1 every second), assuming that the vast majority of scanned ports are actually closed, which they are in practice. So for 10 of our sent probes we receive the "closed" response pretty much immediately and can log the associated port’s state and be done with it. For the other 90 ports we have to wait for our timeout period to expire and have to retry again in one of the following passes, because we don't know if the packet was lost or filtered or whatever.

Now imagine the same scenario where sending our 100 probes takes instead 2 seconds. This would represent the 2K8R2 system running in full-duplex (OK, I know this isn’t double the throughput but I’m just trying to make a point). During that time we may only receive 2 "closed" responses, leaving 98 ports to have to wait for a timeout.

Scale this up to 65536 ports against dozens of targets and you can see how this mounts up.

With the fixed NIC settings this is expected and correct behavior. The fact that it was faster with the "broken" driver was just a quirk of that configuration. Had the NIC been working correctly we would not be here today discussing this problem since all scans would have taken the same (longer) time.
]]>Blog2011-12-17T17:55:18-05:00http://keir.net/blog/files/a5c9bf7e2a74e67aac04916179bfd55e-59.html#unique-entry-id-59http://keir.net/blog/files/a5c9bf7e2a74e67aac04916179bfd55e-59.html#unique-entry-id-59pair.com’s web hosting service for many years, I finally bit the bullet and transferred my DNS domain name registrar from Network Solutions to pairNIC. It was a painless process taking less than a week, the vast majority of that time spent waiting for Network Solutions to relinquish the name.

I’d been planning to do this for years but every time my domain was up for renewal I would inevitably leave it until it was too late to risk moving it or had worried it would be too complicated or error prone.

This time I was determined not to let it pass.

Not only is pairNIC half the price of Network Solutions* and keeps my Whois details private at no extra cost, but I bet I won’t be pressured to renew by being spammed by them every other week starting 6 months prior to my domain expiring.

* Actually I was only charged $10 for the next full year since this was a transferral, so in effect this was less than a third the price of Netsol.]]>Blog2011-12-09T11:45:07-05:00http://keir.net/blog/files/1712a01e58474ec46b0aca41e8873786-58.html#unique-entry-id-58http://keir.net/blog/files/1712a01e58474ec46b0aca41e8873786-58.html#unique-entry-id-58
While they were sitting waiting for their car to finish being inspected they pulled out a phone and did a quick sweep of the company’s WiFi network, to which they were connected after having received the relevant password from the front desk.

Two systems jumped out as interesting, both Dells, according to their MAC vendor IDs. They had TCP port 445 open, meaning they were most likely Windows PCs with file sharing enabled.

They then launched the FileBrowser SMB file access app against one of the systems. Sure enough there were a whole bunch of shared directories and files available, no password required. A little further digging revealed exactly what this system was. It was one of the point of sale devices (cash registers) from the front desk, sitting wide open on the same WiFi network that all of their customers had access to.

Not only is this a catastrophically dumb idea, but it flies in the face of numerous payment card industry regulatory practices and requirements.

No wonder things like this happen.
]]>Blog2011-12-04T09:37:22-05:00http://keir.net/blog/files/8989679f69e12d4d890fb51c449d306f-57.html#unique-entry-id-57http://keir.net/blog/files/8989679f69e12d4d890fb51c449d306f-57.html#unique-entry-id-57
Then all of a sudden, about a week ago, I noticed that the battery was losing charge at a significantly faster rate, without any increase in my usage.

I would leave the phone fully charged, 100%, next to my bed before I went to sleep and 9 hours later in the morning it was at 58%. WTF?

This went on for days, so I began some experiments in order to isolate the cause.

Turn off all unnecessary notifications, alarms, usage reports, auto time zone detection etc.
No change.

Turn off Bluetooth.
No change.

Turn off WiFi.
No change.

This was crazy. No Bluetooth and no WiFi and yet the battery was dropping 30% to 40% overnight.

My last resort, something that in hindsight I should have tried earlier; a full power-off i.e. holding both buttons down for a couple of seconds and sliding off the power, waiting a few more minutes and starting it up again.

I charged the phone back to 100%, turned Bluetooth and WiFi back on and left the phone next to the bed again ready for the morning, fully expecting no improvement.

The percentage charge value the next morning? 99%!!

So, while I am still none the wiser as to the root cause of the abnormal battery drain issue, in my case at least, performing a complete power off/on cycle solved the problem.

My thinking, since I had turned off both Bluetooth and WiFi in my tests, was that power drain through radio use was not the cause. My software engineering background leads me to think that perhaps there was some process caught in a tight loop, sucking up the CPU and in turn draining the battery. A full power cycle cleared out the culprit process. It’s certainly a possibility.]]>Blog2011-11-21T10:55:11-05:00http://keir.net/blog/files/944ef49c762dfc2c1bde89b3e20b8600-56.html#unique-entry-id-56http://keir.net/blog/files/944ef49c762dfc2c1bde89b3e20b8600-56.html#unique-entry-id-56
A very nice feature of their web UI is the ability to see a record of account logon details showing the IP addresses from where your email account was accessed. If Google has detected use of your account from an IP address that it hasn’t seen before it shows a nice big red warning message at the top of the screen and recommends you immediately change your password. Unfortunately it was precisely this kind of message that was presented to me when I logged in.

This is a snippet of my login details showing the offending entry.



Now, I usually access Gmail from home or the near vicinity, which is in Virginia, U.S, so seeing an entry claiming to geo-locate to Oklahoma was a little disturbing. I confirmed that this IP address was a DSL connection originating in that state. Of course I immediately changed my password from its already secure and complex version to an even longer impossibly complex one and checked all of my email rules to ensure they hadn’t been tampered with.

I have a number of questions and observations though.

• I am a security professional and know how to secure my computers and devices. *
• I don’t use computers or devices other than my own to access Gmail and my systems are to the best of my knowledge secure.
• I always use SSL when connecting to Gmail.
• My password was already very strong, long and complex.
• What does Google mean by “accessed”?

It is this last question I wonder about. Was it just an attempt at accessing my account (e.g. trying to guess my password, but failing) or was somebody actually able to fully access my account using a successful login?

I hope it’s the former.

I don’t store any sensitive information in Gmail. It’s mainly used as a back-stop account, a secondary spam filter from my primary (non-Gmail) account so I wouldn’t really have lost any sensitive data. Still, it makes you a little paranoid when things like this happen.

[ * OK, I know I’m not immune but I would hope I stand a better chance than the average user at securing my stuff. ]
]]>Blog2011-11-09T10:59:43-05:00http://keir.net/blog/files/9620a641de74f41b1be27cd217e94367-55.html#unique-entry-id-55http://keir.net/blog/files/9620a641de74f41b1be27cd217e94367-55.html#unique-entry-id-55
All of a sudden the machine locked up and the display started flickering and showing odd colors. I tried rebooting several times but more often than not it didn’t seem to progress much beyond the spinning icon directly after startup.

That was when I realized I could remote-desktop (VNC) into the machine where I could see the login screen/desktop and everything appeared to be working just fine. So that told me it was the video card that was the issue.

I had heard about problems with higher than average failure rates for NVIDIA 8600M GT based older MacBook Pros (mine is an early 2008 model). See here.

Apparently my machine fell within the date range and type of malfunctioning models and supposedly Apple had now extended free repairs to affected systems to 4 years since purchase. Could I be in luck? I made an appointment at the local Apple Store Genius Bar for the next morning.

At the Apple Store they confirmed it was indeed the notorious NVIDIA failure and that it would be a free repair! 3 to 5 days until I would get it back.

This morning I received an email saying my machine was fixed and ready to pickup. A one day turnaround, for free. Now that’s pretty good service!

One slightly odd thing is that it appears that Apple zapped my password. The password in place when I booted it up was now blank. That’s a little sneaky and I wish they could have told me about it rather than me wonder why on earth it didn’t seem to want a password when logging in. I guess they just do it routinely when they encounter a password-protected system (but then I did have a Guest account logon enabled, so why not use that?). Anyway, the password is now reinstated and so far so good.]]>Blog2011-11-01T17:42:55-04:00http://keir.net/blog/files/ba6600d146a5c9f54b49ca9a9eb346a0-54.html#unique-entry-id-54http://keir.net/blog/files/ba6600d146a5c9f54b49ca9a9eb346a0-54.html#unique-entry-id-54Other, where you will find 2 new sections; one for photos and one for books. Both are fairly limited right now but I’ll eventually add to them.]]>Blog2011-10-29T14:05:32-04:00http://keir.net/blog/files/83b620f7394db945f65b4aa285ec01d5-51.html#unique-entry-id-51http://keir.net/blog/files/83b620f7394db945f65b4aa285ec01d5-51.html#unique-entry-id-51RapidWeaver to create and maintain the site which seems to do a pretty good job.

Gone is the “links” page, which was completely outdated and really only served as spam bait for people wanting me to link to their bogus site. No thanks!

Also gone are the donation links. Since I haven’t actually created any new content or maintained the existing software in a very long time I didn’t really think it fair to ask any more.]]>Blog2002-11-16T17:30:45-05:00http://keir.net/blog/files/f85211a2171e7eb8ca26e03cce61642a-50.html#unique-entry-id-50http://keir.net/blog/files/f85211a2171e7eb8ca26e03cce61642a-50.html#unique-entry-id-50Blog2003-03-15T17:30:06-05:00http://keir.net/blog/files/0ab60f71adb1031d2000ab82e98ff7b9-49.html#unique-entry-id-49http://keir.net/blog/files/0ab60f71adb1031d2000ab82e98ff7b9-49.html#unique-entry-id-49Blog2003-04-20T17:29:39-04:00http://keir.net/blog/files/e808cf3013575b1af890e984cda0c75e-48.html#unique-entry-id-48http://keir.net/blog/files/e808cf3013575b1af890e984cda0c75e-48.html#unique-entry-id-48Blog2003-04-27T17:29:08-04:00http://keir.net/blog/files/87d62f477722e964ba7f7458ced9dd02-47.html#unique-entry-id-47http://keir.net/blog/files/87d62f477722e964ba7f7458ced9dd02-47.html#unique-entry-id-47Blog2003-05-06T17:28:42-04:00http://keir.net/blog/files/0ffad31e99f223ae474d307a0dbdb17e-46.html#unique-entry-id-46http://keir.net/blog/files/0ffad31e99f223ae474d307a0dbdb17e-46.html#unique-entry-id-46Blog2003-05-11T17:28:15-04:00http://keir.net/blog/files/9ed25d42d31d0446648e5f8e5fad1fe9-45.html#unique-entry-id-45http://keir.net/blog/files/9ed25d42d31d0446648e5f8e5fad1fe9-45.html#unique-entry-id-45Blog2003-05-18T17:22:19-04:00http://keir.net/blog/files/7bf761c65b9ac311b36863f42c3c1378-44.html#unique-entry-id-44http://keir.net/blog/files/7bf761c65b9ac311b36863f42c3c1378-44.html#unique-entry-id-44Blog2003-06-08T17:21:50-04:00http://keir.net/blog/files/18f93cb804245e4790ec3c2ba9936281-43.html#unique-entry-id-43http://keir.net/blog/files/18f93cb804245e4790ec3c2ba9936281-43.html#unique-entry-id-43Blog2003-06-22T17:21:20-04:00http://keir.net/blog/files/ddf1d46ab5776bfb0db8a5a45ade707e-42.html#unique-entry-id-42http://keir.net/blog/files/ddf1d46ab5776bfb0db8a5a45ade707e-42.html#unique-entry-id-42Blog2003-06-28T17:20:52-04:00http://keir.net/blog/files/1f4c57e484b7acf57529dd12479944c7-41.html#unique-entry-id-41http://keir.net/blog/files/1f4c57e484b7acf57529dd12479944c7-41.html#unique-entry-id-41Blog2003-07-03T17:20:25-04:00http://keir.net/blog/files/af40f2184b6686a2706766c411315aef-40.html#unique-entry-id-40http://keir.net/blog/files/af40f2184b6686a2706766c411315aef-40.html#unique-entry-id-40Blog2003-07-09T17:19:56-04:00http://keir.net/blog/files/a6e98d11a677908ad59b022c908db7c5-39.html#unique-entry-id-39http://keir.net/blog/files/a6e98d11a677908ad59b022c908db7c5-39.html#unique-entry-id-39Blog2003-08-01T17:19:24-04:00http://keir.net/blog/files/9d9f4dd347cc36c53a6228465a87709c-38.html#unique-entry-id-38http://keir.net/blog/files/9d9f4dd347cc36c53a6228465a87709c-38.html#unique-entry-id-38Blog2003-08-10T17:18:54-04:00http://keir.net/blog/files/c7439b151fcb50e1e78828dc5fa84b86-37.html#unique-entry-id-37http://keir.net/blog/files/c7439b151fcb50e1e78828dc5fa84b86-37.html#unique-entry-id-37Blog2003-08-17T17:18:21-04:00http://keir.net/blog/files/333cf02422b22e536c66e114ae7f1517-36.html#unique-entry-id-36http://keir.net/blog/files/333cf02422b22e536c66e114ae7f1517-36.html#unique-entry-id-36Blog2003-08-31T17:17:22-04:00http://keir.net/blog/files/0061a1ac43cfe58d0d9cdf32078229ef-35.html#unique-entry-id-35http://keir.net/blog/files/0061a1ac43cfe58d0d9cdf32078229ef-35.html#unique-entry-id-35Blog2003-11-02T17:16:52-05:00http://keir.net/blog/files/420288c08d49f277ae6ddd92f94413e6-34.html#unique-entry-id-34http://keir.net/blog/files/420288c08d49f277ae6ddd92f94413e6-34.html#unique-entry-id-34Blog2003-11-06T17:16:22-05:00http://keir.net/blog/files/bbb8a56a234cc33ef899605048876e5f-33.html#unique-entry-id-33http://keir.net/blog/files/bbb8a56a234cc33ef899605048876e5f-33.html#unique-entry-id-33Blog2003-11-11T17:15:54-05:00http://keir.net/blog/files/6ca94211f7131f89f723180a970a626f-32.html#unique-entry-id-32http://keir.net/blog/files/6ca94211f7131f89f723180a970a626f-32.html#unique-entry-id-32Blog2003-11-21T17:15:29-05:00http://keir.net/blog/files/20c3285e4cbe499025e5d05ae2af4a72-31.html#unique-entry-id-31http://keir.net/blog/files/20c3285e4cbe499025e5d05ae2af4a72-31.html#unique-entry-id-31Blog2003-12-14T17:14:58-05:00http://keir.net/blog/files/7d3fbfeead3bf7b6cb67f7263623bb26-30.html#unique-entry-id-30http://keir.net/blog/files/7d3fbfeead3bf7b6cb67f7263623bb26-30.html#unique-entry-id-30Blog2003-12-24T17:14:23-05:00http://keir.net/blog/files/52357ccab400da8f2a5ba96fbe1b5a15-29.html#unique-entry-id-29http://keir.net/blog/files/52357ccab400da8f2a5ba96fbe1b5a15-29.html#unique-entry-id-29Blog2004-01-01T17:13:52-05:00http://keir.net/blog/files/ccbb83071eed3470909291008ed3a1da-28.html#unique-entry-id-28http://keir.net/blog/files/ccbb83071eed3470909291008ed3a1da-28.html#unique-entry-id-28K9 Version 1.20 released.]]>Blog2004-01-03T17:13:01-05:00http://keir.net/blog/files/554d7f74c69bc64e1a4a9839f0f01f8f-27.html#unique-entry-id-27http://keir.net/blog/files/554d7f74c69bc64e1a4a9839f0f01f8f-27.html#unique-entry-id-27Blog2004-01-11T17:12:04-05:00http://keir.net/blog/files/f50b8b8a051eac3101a7edcf6e49ca2b-26.html#unique-entry-id-26http://keir.net/blog/files/f50b8b8a051eac3101a7edcf6e49ca2b-26.html#unique-entry-id-26Blog2004-01-25T17:11:37-05:00http://keir.net/blog/files/7edbf4d93ba91214254ca33bcbe66858-25.html#unique-entry-id-25http://keir.net/blog/files/7edbf4d93ba91214254ca33bcbe66858-25.html#unique-entry-id-25Blog2004-01-31T17:11:07-05:00http://keir.net/blog/files/35885c560f03d6fe1ae1eb6f9045bac4-24.html#unique-entry-id-24http://keir.net/blog/files/35885c560f03d6fe1ae1eb6f9045bac4-24.html#unique-entry-id-24Blog2004-02-08T17:10:30-05:00http://keir.net/blog/files/adeb7c83823387a0b56ba9893b0fc95a-23.html#unique-entry-id-23http://keir.net/blog/files/adeb7c83823387a0b56ba9893b0fc95a-23.html#unique-entry-id-23Blog2004-03-13T17:10:00-05:00http://keir.net/blog/files/ace9c8bd242bfb3e59e53636510dfb1d-22.html#unique-entry-id-22http://keir.net/blog/files/ace9c8bd242bfb3e59e53636510dfb1d-22.html#unique-entry-id-22Blog2004-04-05T17:09:32-04:00http://keir.net/blog/files/ba7119e9cabda1bb7e3cbe64897957ce-21.html#unique-entry-id-21http://keir.net/blog/files/ba7119e9cabda1bb7e3cbe64897957ce-21.html#unique-entry-id-21Blog2004-04-18T17:08:48-04:00http://keir.net/blog/files/1194efbe818e76737de422a274cd780d-20.html#unique-entry-id-20http://keir.net/blog/files/1194efbe818e76737de422a274cd780d-20.html#unique-entry-id-20Blog2004-04-24T17:08:05-04:00http://keir.net/blog/files/ce7a64c7b3d596c6fb3d3fea5ec37c33-19.html#unique-entry-id-19http://keir.net/blog/files/ce7a64c7b3d596c6fb3d3fea5ec37c33-19.html#unique-entry-id-19Blog2004-04-24T17:07:35-04:00http://keir.net/blog/files/e757cdfda0d167c270ab3ca70ec2e17b-18.html#unique-entry-id-18http://keir.net/blog/files/e757cdfda0d167c270ab3ca70ec2e17b-18.html#unique-entry-id-18Blog2005-01-04T17:06:46-05:00http://keir.net/blog/files/17b178e909a074acb363c50e1aec1c00-17.html#unique-entry-id-17http://keir.net/blog/files/17b178e909a074acb363c50e1aec1c00-17.html#unique-entry-id-17Blog2005-01-16T17:06:05-05:00http://keir.net/blog/files/2f4650a100c1f9ea5c6faa7feac600d8-16.html#unique-entry-id-16http://keir.net/blog/files/2f4650a100c1f9ea5c6faa7feac600d8-16.html#unique-entry-id-16
Retired BDE Remove. This was largely redundant in light of the multitude of other freeware programs that can remove all kinds of spyware.]]>Blog2005-05-07T17:05:33-04:00http://keir.net/blog/files/b1659969ef44a78c3fa39708e9e9cd7d-15.html#unique-entry-id-15http://keir.net/blog/files/b1659969ef44a78c3fa39708e9e9cd7d-15.html#unique-entry-id-15Blog2005-09-10T17:04:43-04:00http://keir.net/blog/files/d511218f56038bda608e42db636bea84-14.html#unique-entry-id-14http://keir.net/blog/files/d511218f56038bda608e42db636bea84-14.html#unique-entry-id-14
A small GUI tool to compute MD5, SHA1 and CRC32 hashes of files.]]>Blog2005-09-15T17:04:09-04:00http://keir.net/blog/files/2eb00efc6d1e032ca3eeda46121c0acd-13.html#unique-entry-id-13http://keir.net/blog/files/2eb00efc6d1e032ca3eeda46121c0acd-13.html#unique-entry-id-13Blog2005-10-27T16:54:40-04:00http://keir.net/blog/files/58dec3b3fe3bff8b10583d471461535b-12.html#unique-entry-id-12http://keir.net/blog/files/58dec3b3fe3bff8b10583d471461535b-12.html#unique-entry-id-12Blog2006-01-08T16:53:55-05:00http://keir.net/blog/files/c2e1919044f04c7b812597f77276ea80-11.html#unique-entry-id-11http://keir.net/blog/files/c2e1919044f04c7b812597f77276ea80-11.html#unique-entry-id-11Blog2006-09-01T16:52:24-04:00http://keir.net/blog/files/1f890161d5ffb59831d6431843effc65-10.html#unique-entry-id-10http://keir.net/blog/files/1f890161d5ffb59831d6431843effc65-10.html#unique-entry-id-10Blog2006-10-14T16:51:53-04:00http://keir.net/blog/files/57f848221436c0172653fb77897186ec-9.html#unique-entry-id-9http://keir.net/blog/files/57f848221436c0172653fb77897186ec-9.html#unique-entry-id-9Blog2006-12-09T16:36:30-05:00http://keir.net/blog/files/a77c81b764840ab1040ae0f63044ac72-8.html#unique-entry-id-8http://keir.net/blog/files/a77c81b764840ab1040ae0f63044ac72-8.html#unique-entry-id-8
A small GUI tool to show netstat information.]]>Blog2007-04-22T16:34:57-04:00http://keir.net/blog/files/6ba6f71f9d59362ee38ed2ddc785ab72-7.html#unique-entry-id-7http://keir.net/blog/files/6ba6f71f9d59362ee38ed2ddc785ab72-7.html#unique-entry-id-7
A command line tool to crack Microsoft Visual SourceSafe passwords.]]>Blog2007-09-16T16:34:06-04:00http://keir.net/blog/files/387b6459c96d1e338365b54859bb7a1d-6.html#unique-entry-id-6http://keir.net/blog/files/387b6459c96d1e338365b54859bb7a1d-6.html#unique-entry-id-6Blog2007-09-19T16:33:11-04:00http://keir.net/blog/files/e9c97d69f083efce984d361226cf3a56-5.html#unique-entry-id-5http://keir.net/blog/files/e9c97d69f083efce984d361226cf3a56-5.html#unique-entry-id-5Blog2007-09-25T16:32:09-04:00http://keir.net/blog/files/e55092c7889c6a1a31a08e3ce37a2817-4.html#unique-entry-id-4http://keir.net/blog/files/e55092c7889c6a1a31a08e3ce37a2817-4.html#unique-entry-id-4Blog2008-06-23T16:27:58-04:00http://keir.net/blog/files/431e084b5f0e26a338be1a7daa98c08d-1.html#unique-entry-id-1http://keir.net/blog/files/431e084b5f0e26a338be1a7daa98c08d-1.html#unique-entry-id-1Blog2011-10-19T11:21:04-04:00http://keir.net/blog/files/3f57a5cb54d30fe5a817d1aa99aeb318-0.html#unique-entry-id-0http://keir.net/blog/files/3f57a5cb54d30fe5a817d1aa99aeb318-0.html#unique-entry-id-0
Also seen here are announcements from years gone by regarding released versions of my software for historical purposes.]]>