
I just read this report on Somebody Think of the Children having just seen it commented on by Cameron Reilly on Twitter and shared by Alex in Google Reader. I’m speechless. Game over man, game over.

I just read this report on Somebody Think of the Children having just seen it commented on by Cameron Reilly on Twitter and shared by Alex in Google Reader. I’m speechless. Game over man, game over.

From the I Can’t Believe They’re Serious department, Bruce Schneier has blogged about a hilarious memory key product (link fixed) that doesn’t get its security from sound, well implemented cryptography, but from.. get this… a two wheel physical combination lock that hides the contact pins!
Back in 2006 I posted some of my favourite Bruce Schneier facts. Here we are in 2010 and I still read ones that make me laugh out loud!

Has Google Reader (or Google Accounts in general) implemented a stricter timeout system for logins, does anyone know? I’ve been automatically logged out several times today with the above message cheerfully displayed when it never used to happen before.
I’m thinking it could be my newly cleaned out cookie whitelist for PermitCookies in Firefox, but just want to make sure. Could Buzz have anything at all to do with it perhaps? If they are timing out sessions earlier it could be beneficial for security but I tend to have Reader permanently open in a tab and I’d hate to have to re-login every hour or so.

Having just lambasted (sounds like an old school Shaggy song) cloud computing for data breaches and privacy concerns, I think it helps to remind myself/ourselves that “traditional” in-house server systems aren’t exactly bullet proof either. Damned if you do, damned if you don’t.

Today’s epiphany. Kind of embarrassing that I’ve been using OpenSSH for this long without doing this.
SSH with pre-shared keys is simply a pleasure to use. The fact the security is much better is just an added bonus ;)
Is that how you spell Epiphany? Let me go check the Gnome project page :).

Having only just sat at Starbucks to do some programming and cleaning out my desktop (I let far too many files accumulate) I accessed the free WiFi and launched Firefox only to see the above dialog presenting me with a NoScript update. Problem is, I’m connected to the WiFi hotspot but not to the open internet! Spooked out stuff.
![]()
While my dad, sis and I were on our Eurotrip over the New Year holidays (photos coming soon) we were placed in self imposed 24-hour-instant-Twitter-news exile, which to tell the truth was kinda refreshing. The only thing we had to worry about in Europe was being buried in a freak Irish, German, French, Czech or Austrian snowstorm, or finding plastic explosive in our baggage from Slovakia on arrival in Dublin. But I digress.
Logging onto one of the shared computers at the UniSA Mawson Lakes campus this morning I got this error message. Again.

As I said with the Ghostery Firefox extension back in May (Ghostery Mozilla Firefox extension review), it bowls me over when I go to some sites to see just how much sneaky crap is going on behind the scenes, and how most people simply have no idea. With NoScript, I’m starting to see the same thing, and it’s rapidly getting much worse.