So that’s what happens…

Today I did something I haven't done in a long time: I downloaded and installed some unsigned code while running as a local administrator on my home computer.

I had to stare at the Security Warning dialog from Windows for quite a few moments before I decided that I really wanted to install software from Unknown Publisher. I almost expected my machine to catch on fire as I clicked the Run button... but surprisingly enough the application seemed to install without incident (or so I hope!).

So why did I do it? Because realistically I had no other choice. It was either that or live without the software, and I wanted to use the software. Just like the other week when I had to install an unsigned driver for some hardware I purchased. The manual helpfully told me how to turn off driver signing (uh, thanks... I guess) but neglected to say I should turn it back on again afterwards! And it's not like I'm going to take my hardware back to the store and say "I don't want to use this cool device because the driver isn't signed."

Sometimes you just have to take calculated risks. Luckily for me I think I got by alright this time.

In other news, Alcazar's new single Alcastar is incredibly good -- especially the Soundfactory Starstruck Anthem. Buy it now! 🙂

Comments (2)

  1. Riccardo says:

    "Unsigned code" is so common that i can’t imagine a situation within you have not to deal with it…

  2. Heh-heh.

    I get that feeling too when I want to run something as local admin. It seems that it will still take time to get *some* software vendors to stop making software that installs–nevermind runs– as admin.

    If the software I’m about to run gives me enough heebee jeebies, I tend to run it under VMWare (err… I mean, Virtual Server :), and restore if things go bad.

    I’m wondering if Windows can be enhanced to give apps a proper sandbox that can be played in, where it thinks that the whole OS is under its control. …. HmmmmmMMmM. That’d solve some things. Maybe.


Skip to main content