Why go to all the technical trouble of stripping DRM controls from songs, when all you need do is:

1. Play the DRM controlled song on a device supporting the DRM.
2. Record the analog sound using high-quality audio cables to a non-DRM controlled format (like OGG or MP3).
1. Audacity can help with such tasks.
3. Distribute (for legal purposes only ;) ).

But it's ok, Microsoft is working on the problem. Soon there will be DRM bouncers who will be authorised to hit you if you try this technique. Cutting off their legs will be considered 'reverse engineering' and a violation of the DMCA.

This scares me, I mean really scares me. How can the people designing our AV software not understand that unknown malware is their biggest problem? Surely someone has explained the problems of 'enumerating badness' to them?

But wait, they are angry because someone wrote malware, that's all. It seems AV people take blacklisting to heart. What Consumer Reports should have done is written a new packer for existing malware, then we could have bypassed that rule :)

Malware is to an AV product as a test case is to a program. Could their rule to not create malware be why they are so bad at detecting new malware, or could it be because it is a bloody hard problem and they don't want to loose market share by admitting it?

Right, sceptic out. I'm off to write my own self-modifying OS in C.

Today a plane flying from London to somewhere in America was diverted to somewhere else in America by fighter jets. Why? Because of an 'agitated' woman carrying a screwdriver and matches.

Does this seem a bit dissproportionate to anyone? I can see the threat-o-meter logic now:

Screwdriver + maches + agitation = Scramble the Jets!

Not to mention the fact that with all the heightned security hoo-haa, she still managed to get a screwdriver onto the plane, it isn't exactly made of plastic, if you get my drift.

So you finally got local administor access on your Windows machine. The problem is that you're part of a domain with restrictive group policies and you really want to change your wallpaper, but remain part of the domain.

After some rooting around in the windows registry I found out where the nasty group policy hides. Just nuke everything in these keys, or if you have other intentions, directly modify them here:

HKEY_CURRENT_USER\Software\Policies
HKEY_CURRENT_USER\Software\Nicrosoft\Windows\CurrentVersion\Policies

HKEY_LOCAL_MACHINE\SOFTWARE\Policies
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies