FireFox 3 Bug??

Like most security conscious people I use Firefox (FF) for my everyday browsing on the Internets. So when the Mozilla guys released version 3 I installed it on all my machines (2 Windows and 2 OSX platforms).

It was a bit getting used to. The underlying FF part had been changed. Bookmarks, history etc are all stored in sqlite databases. So no more flatfiles. This took me a couple of hours to figure it out, but finally I got 'there'.

Using FF was business as usual... Apart from one very annoying bug; Opening new windows (not new tabs) results often in an empty bookmarks bar. And this is happening on Windows and OSX versions of FF.
The bookmarks are 'there' but not click-able. Using the right mouse button (on OSX: ctrl-mouse click) on the bookmarks bar and selecting 'Open All in Tabs', FF opens every bookmark in the bar.

The only way of restoring the proper bar is the completely shutdown FF and restart it. After that it works for a certain amount of time.

The problem isn't isolated to my environment. Just google on the issue, and you'll find more people. There's one suggestion I haven't tried yet. Starting with a fresh/clean profile, but I do need my settings/passwords/bookmarks. I'm lost without those :(

UPDATE: I tried a new profile, and this seemed to work. After this I started to repopulate the new profile with the old settings, etc. Everything went fine until the point where I added the extensions. It seems that even old / not active extensions (SwitchProxy in my case) are still able to f*ck things up.

Windows/Office Frustrations

The title should cover the topic appropriately.... The last couple of days there's this delay on opening Office documents on my work laptop. Every MS-Word or Excel document I open (by double clicking the document) takes approximately 25 to 30 seconds to open.

Using tools like procmon (formerly known as filemon from SysInternals) displayed nothing interesting. Apart from a 15 to 20 seconds delay between the WINWORD.EXE appearances in the logging.
Since this nagged the hell out of me, I tried some stuff (in a non-chronological order);

• Removed McAfee AV
• Removed all tooling I installed in the last couple of days
• Removed  MS-Word
• Removed Office 2003 completely
• Removing all references to Office, MS-Word or Excel in the registry, and on the filesystem.

Running Word with the /a switch or even typing winword.exe c:\test.doc works fine. Everything works, except the default opening of a file by double clicking it.

Someone suggested to add another user on the system and try it with that user account. So I did. I logged on as the new user and every document launched as it's supposed to do :-) . So I logged out, and tried the original user, and guess what? The document opened lightning fast. I couldn't be more happy, because I didn't feel like reinstalling the entire system.

After working a couple of hours I restarted the system (application update), and everything went back to 'normal'... Opening documents took forever again.....
It seems that launching Word from a FRESH user account resets something. Everything afterwards works fine, just as long as you don't reboot... And since it's Windows...... Well, Friday is gonna be a re-installment day. Am I looking forward to that (that's something of a rhetorical thing).

FireFox 3 Dialog Boxes

Firefox is the default browser on all my platform, and every once in a while I run into strange dialog boxes.
E.g., this evening I updated some digital certificates for the test environment of VeriSign MPKI backend. These certificates are issued by a (private) VeriSign CA. So there's no trust by default.

After generating the keypair in FireFox 3 I got the positive dialog box as showed below.

No problem so far, but the next dialog box 'scared' me a little;

This dialog box, or at least the result, would remove (or delete) the certificate I just generated. The issueing CA is not installed in FireFox (or on the machine itself for all it matters). But in fact the certificate was installed in the Crypto/Certificate store of FireFox, and I could use it to access the VeriSign test backend.

So, eventhough, FireFox warns the user that the content will be deleted (or not added), it doesn't exactly does that at all. Let's see if I can file a bug report, because this occured on all 4 certificates I generated/imported.

Nikon D300 Firmware Update v1.03

Nikon released a new firmware update (v1.03) for their D300 DSLR. The new firmware should fix certain battery related issues.

• Windows version
• Mac/OSX version

Be sure to get it.

Nokia N95

The Nokia E61i is old. Well, ever since I got a Nokia N95 from my boss. So no longer a privately owned phone (with a company SIM), but a new shiny N95 :).

First impression; plastic fantastic, but a fast plastic fantastic phone. A faster CPU, HSDPA instead of 'regular' UMTS, and a 'normal' keypad instead of a QWERTY keyboard (which is not an improvement!!)

The OS (Symbian S60) is the same as the OS on the E61i, so no real surprises on that part. Even the backup with Nokia Phone Manager restored on the N95. New features were also included;

• upload images to Flickr
• nokia maps
• built-in GPS

The only real bummer is the lame Nokia Phone Manager software. That application just won't work properly (it could also be that the crappy Windows OS is helping a hand).

Updating Capture NX on Mac

When I bought my Nikon D300, I got a free copy op Capture NX (v1.3.0). After installing, the application reminded me to update. There were a couple of new versions available (current version is 1.3.3).
This is were the quest began......

The Nikon Update application kept crashing on me. 50MB downloads took over three hours (before crashing), while a single download from the support pages would take 5 to 10 minutes. So I needed to get the files from the web instead of using the updater.

First, the D300 was bought in the Netherlands, so you might think that the software would also be the Dutch version. I wouldn't know this because I install everything in English (if there's a choice). So I downloaded the Dutch updates from the Nikon support pages.

Note: I used the 'Dutch' CD which came with the camera.

None of the updates worked (Error: No version of Capture NX was found)....

I literally downloaded 12 different versions from different continents. Finally, I found a 1.3.1 update (a file called cnx131_en.dmg) which worked. So I needed to get English versions of the software. Not US, or Canadian versions, but English versions.

After this it was easy; Created an account on the UK Nikon support website and found Nikon Capture NX v1.3.3 for OSX. This update worked. So finally, after a gazillion downloads, multiple crashes, and 5 hours well spend, I got Capture NX v1.3.3 up and running.....

So, even if your camera is officially purchased in the Netherlands, you need to get the updates from the UK.

UPDATE: It seems that I'm not the only one who ran into this. I keep getting referers from some fora around the Internet.
I think that if you're running Windows instead of OSX you might have similar problems. So yet another crossplatform solution :)

CiscoVPN Error 51 Annoyance

The CiscoVPN client (v4.9.01.0100) for Apple OSX throws an error every once in a while. Mainly when I just rebooted, or when I was forced to quit some hanging application (which also occurs on Macs). The error is:

Error 51: Unable to communicate with the VPN subsystem

Somehow, the VPN software looses contact with the network adapter (wired AND wireless). After this there are two things you can do;

1. Reboot
2. or restart the Cisco VPN Service manually.

The first is kinda obvious (it's almost a MS Windows strategy :)). The second one is done via the Terminal (Finder -> Applications -> Utilities -> Terminal). Just type the following command (followed by your password);

sudo /System/Library/StartupItems/CiscoVPN/CiscoVPN restart

The thing I don't understand is; Why hasn't Cisco incorporated this in the VPN client?

IF (Error 51 == TRUE)
DO CiscoVPN.restart

It seems that this 'bug' is present since the release of the Mac OSX version of the software.

OpenSSH Vulnerabilities

It seems that public key authentication isn't as save as you might have thought. That is if you're using a Debian based OpenSSH solution. This package can be found in many Linux distributions like;

• Debian (duh ;) )
• Ubuntu
• Kubuntu
• etc.

The problem is that the random number generator (which is of vital importance in generating key-pairs) isn't as random as you might think. It seems that there are only about 30.000 combinations in this specific generator. This leaves the door wide open for brute-force attacks.

So, the first you must do is update your OpenSSH software, and generate new keypairs for all devices / users which might have keys which were generated with the vulnerable OpenSSH software. Softwarepackages depending on OpenSSH are;

• OpenVPN
• DNSSEC
• OpenSSH
• Certificates used in TLS connections
• etc.

More info on the subject can be found here [1, 2, 3].