Spotify invites

Edit: All invites have been taken. I might post more later.

Feel free to grab a Spotify.com invite if you don’t already have one. If one fails, try the next on the list.

• VyHkdcCHb6TspB7U


• dskxzDyqU4SyCyFN


• yCsuuViMazBAMYEL


• xRDRaZtXXjj4qRKB


• 2fRu7E7hy5TG358p


• zGJxBkiGchaKFxR7

Incredible incompetency

[Disclaimer: This article is only based on information available through the Norwegian media (thus the links in Norwegian). It’s accuracy is limited to their accuracy combined with my personal understanding of the matter.]

Thursday the 12th of March, more than 1000 computers belonging to the Norwegian police were infected by the computer virus Conficker.

Stop and think! Self-updating, remote controllable, known to be malicious code running on the police’s computers. Maybe they were all innocent workstations with no important information?

I’m afraid not. According to reports, the systems for daily operations of the police departments were unavailable. Passports could not be emitted. Border controls could not check visitors passports against their registries. The unavailability of these services is probably bad, but this also means that this malicious code running on their computers had open access to information about criminal cases, filings, citizen databases, etc.

So, how did this happen?

The Conficker worm spreads through a buffer overflow error in most versions of the Windows operating system. This error was fixed in a critical patch released by Microsoft the 23rd of October 2008.

Why didn’t the police install this patch on their computers? They host their system on Windows NT 4.0. This is an operating system released by Microsoft in 1996 that had it’s last available support agreement terminated in 2004. By the end of that year, Microsoft stopped fixing known security vulnerabilities in the OS, and stopped testing it against new vulnerabilities.

Running NT 4.0 in 2009 is stupid. Using it for hosting operational systems with extremely confidential data and high availability demands is neglect.

So, how did they handle this crisis? Did they shut down all systems with suspected infection and wiped their hard drives with a fresh image that had gotten the vulnerable services secured?

According to the press, the virus continued spreading today and has made systems respond slowly. Espen Strai from Politiets data- og materielltjeneste (PDMT) [The police service for data and equipment] has explained that “the challenge is to shut down the infected PC’s and run antivirus programs while the system is still running”.

You cannot trust a computer once it has executed malware. The only option to clean it reliably is to wipe the drive and install an image that is known to be clean.

I don’t know the complete picture behind this story, nor have I read all of the vast information available in the press. But it is clear that this is a serious case of neglect and I personally hope that criminal charges will be filed against the ones responsible for keeping alive this fundamentally insecure and antiquated system.

How to integrate Spotify into Last.fm (Firefox)

Trick to get direct links to Spotify searches from the Last.fm web page (very useful for e.g. your personal recommendations):

1. Install Greasemonkey: https://addons.mozilla.org/en-US/firefox/addon/748
2. Install this script: http://emil.hesslow.se/spotify/spotify__lastfm.user.js

Note the little green notes you now get next to artists, albums etc.

Make Spotify work with Logitech SetPoint

Edited 25.03.2011 to match current version of Logitech SetPoint.

If you use a Logitech keyboard with media keys (such as my Logitech Elite Media Keyboard), you might need to do some tweaking to make the media keys work with Spotify (play, pause, stop, skip). This tweak assumes that you use the latest version of Logitech SetPoint (currently v 6.20.50) in Windows 7 (Vista may also work).

You will probably notice that media keys work well when the Spotify window has focus, while they work unreliably (may pause but not play again) when the window is either minimized or behind other windows.

The procedure to fix this is as follows:

1. Close Logitech SetPoint by right-clicking the icon in the system tray.
2. Open notepad as administrator (right click and Run as administrator).
3. In notepad, open the file "C:\Program Files\Logitech\SetPointP\players.ini" (your folder may be named SetPoint instead of SetPointP on older versions or upgrades). (Hint: If you don't see the file, you must select "All Files" in the drop down that says "Text Documents)
4. At the end of the section [Players], add the following line:
   spotify=wac,spotify.exe,SpotifyMainWindow,xxx,xxx,xxx,xxx,xxx,xxx,xxx,0,1,Spotify
5. Save the file. (If this fails or the Save As dialog pops up, this is probably because you didn’t run notepad as admin. Since this is inside the Program Files directory, you need to be admin to edit.)
6. Launch SetPoint again ("Mouse and Keyboard Settings" in the start menu or restart the system) and verify that the media keys now work better.

PS. To do the same for foobar2000 v0.9.6.2, the line to add is as follows:
foobar2000=wac,foobar2000.exe,{97E27FAA-C0B3-4b8e-A693-ED7881E99FC1},xxx,xxx,xxx,xxx,xxx,xxx,xxx,0,1,Foobar2000

The joy of IS and high ISO

450D, EF-S 18-55mm f/3.5-5.6 IS @ 18mm, f/3.5, 1/10 s, ISO 1600, no tripod, all natural lighting (including nearby lamp-post).

Obviously it would have been better with a smaller aperture and lower ISO, but tripod was not an option at that moment (since the ferry was about to arrive).

Taken at Ørsneset (Sykkylven), Norway.