SafeSign and Apple OSX Snow Leopard

Last week I got an e-mail from one of the product managers @ AET Europe regarding the availability of SafeSign / Tokenlounge for OSX Snow Leopard.

The content of the e-mail wasn't very encouraging.... It seems that the Snow Leopard of SafeSign / Tokenlounge release is delayed by a bug in the Apple Keychain;

---------
We use systemkeychain -T to create a login keychain (for a new FV user) associated with our token. When trying to unlock this newly created keychain during login with the smartcard, we get prompted with the "unable to unlock login keychain" panel - as you have observed -.
This is basically our main concern, as this was perfectly running under 10.5. Any idea why the system wants to update the login keychain password, prompting the user with that panel???

What we have discovered beside, is that when you click Create New Keychain on that panel, the keychain gets encrypted with the PIN of the smartcard instead of the RSA key, which is a major security issue (Same behavior if you click Update Keychain Password)...
You can easily verify this last issue by removing your smartcard, launching Keychain Access and entering your PIN code to unlock the keychain...

Once again, we didn't have this kind of problems with Leopard.

As long as this issue isn't resolved, there will be no version for Snow Leopard. The (security) risk is just too big.
-------------

So, we need to be patient, and wait till Apple solves this. In the mean time, when you need the SafeSign software for your every day work, you shouldn't upgrade to Snow Leopard.

Check the follow-up on the original SafeSign post for the availability on the Leopard version of SafeSign / Tokenlounge.

Microsoft Haunted by 17-year old 'feature'

It looks like that every Windows version is susceptible to a 17-year old 'feature' that could give hackers access to your computer. The 'feature' exist since Windows v3.51, which dates from the last century (this way it looks even older :-) )

The person (Tavis Ormandy) who discovered this feature did a full disclosere which can be found here. So you'd better start watching your 3.51 Operating Systems (and above).

Major Wordpress 2.6 Bug

A couple of days ago I upgraded to Wordpress v2.6. After the upgrade I opened the blog, and added a new post. Both of those actions worked properly.

After the upgrade I noticed a major decrease in comment and trackback spam. But today I discovered the real reason why comments AND page views were close to zero.

There's a bug in Wordpress 2.6 where the permalinks are not working correctly. If you're using permalinks with the date, name, etc. (e.g. /index.php/switched-to-mac/) you get a 'Not Found' error. A definite WTF moment.

When you change the permalinks setup in the wordpress admin pages to default the pages/posts are accessible again. It seems that the issue is known and will be fixed in Wordpress 2.6.1. Untill then, most of the Google search results which end up on my website will result in a 'Not Found' error.

I would go back to an earlier version if I could. After the upgrade (which I thought that worked correctly) I removed the 2.5 installment... Yet another lesson for the future.

UPDATE: the pageviews are returning to normal :)