Roll Over, Play Dead

Among the many, many things this could be in your system, I (re)discovered that a Hauppauge WinTV PVR350 was installed in my computer after a recent mobo swamp and Windows reinstall! Grab the drivers, install, and the ugly yellow exclamation will disappear!

Great article from Bruce Schneier on anonymity, privacy, and how both are hard to come by on the WWW. Be sure to read page 2 of the article, where he discusses research on how you can be personally identified by your writing/posting style. Scary stuff indeed.

Does what happens in the Facebook stay in the Facebook?

The answer, unequivocally, is no.

Almost a year ago I touched on this same topic.

I just couldn’t figure it out:  after numerous attempts to install Win2k3 Service Pack 1, I continued getting the 0x8007F0F4 error through Windows Update.  I read a few newsgroup posts and decided to download the network installation SP1 package in hopes that I was just having trouble with the WU services.  No joy…except when using the network install, the error messages I got were even less helpful.  No amount of Googling or newsgroup searching seemed to help.  After quite a hassle and no effective leads, I was ready to give up on Windows 2003 SP1. 

Luckily (or so I thought) Win2k3 SP2 was released and my problems were solved!

Wrong.

The same error was continuing to pop up when using the WU service:  0x8007F0F4

Google and the newsgroups were even less help in relation to SP2.  Most problems centered around Windows XP SP2 and the 0x8007F0F4 error, which of course didn’t apply because I’m sure my servers aren’t on battery power.

When I checked the %windir%\WindowsUpdate.log I couldn’t find much to go on except "Update is not allowed to download due to regulation." 

Normally, it seems, the "regulation" problem happens when too many clients try downloading patches all at once.  That, or your Windows license is invalid.  For me, however, the problem occurred over and over, spanning at least a couple months (the log overwrites itself after a while) and I knew our enterprise license was still valid.

I continued getting 0x8007F0F4 errors no matter what time of day I attempted the download through WU.  Finally I decided to try the network installation version of SP2 and I finally got a reasonable error message:

Setup has detected that the Distributed Transaction Coordinator (MSDTC) service is disabled.  The MSDTC service is required for the successful installation of Microsoft Windows Server 2003 Service Pack 2 (SP2).  Please enable the MSDTC service, and then restart the installation of Windows 2003 SP2.For (sic) more information about enabling the MSDTC service, contact your network administrator.

Luckily I was the network administrator and I had a slight clue about the next step.  A quick trip to the Services Manager allowed me to set the MS DTC service to "manual" and I was back in business after starting DTC!

Why did was DTC disabled in the first place?  The lockdown guide I used a few years ago suggested disabling DTC due to the chance of exploitation.  Evidently, you can operate normally for years, receiving every other update except Service Packs, with MS DTC disabled.

I’d love to find out why this is the case.  But then again, ignorance is bliss.

Thanks for nothing, MS.

The new Win XP-based computer I built was up and running for more than 43 days (over 1,043 hours to be exact) when it received an auto-update that forced its shutdown.

Unbelieveable.  I haven’t had a Windows machine run that long continuously since Win NT 4.0.  Too bad, too, because I know it had a lot left in it.

 This new system has been rock stable and eats anything I throw at it:

• 2 GB G-Skill RAM with 4-4-4-12 timings
• AMD Athlon 64 X2 3800 (socket AM2)
• BFG Nvidia 7600GT with 256 MB DDR3 RAM (overclocked from the factory)
• Asus M2N-SLI Deluxe motherboard

Next steps:  Disable the auto-restart feature after auto-update.

Interesting article from the Cato Institute on how fake IDs are saving lives around the world: 

Cato-at-liberty » Fake IDs Save Lives

Too many wrongly characterize the debate as "security versus privacy." The real choice is liberty versus control. Tyranny, whether it arises under threat of foreign physical attack or under constant domestic authoritative scrutiny, is still tyranny. Liberty requires security without intrusion, security plus privacy. Widespread police surveillance is the very definition of a police state. And that’s why we should champion privacy even when we have nothing to hide.

Wired News: The Eternal Value of Privacy

For all of you in LE and those interested in psychology, here’s a bit of a crazy study done by Stanford University in the 70’s IIRC.  They "jailed" a few college guys and put a few college "guards" in charge of them.  The study was slated to last nearly a week but was cut short after an attempted jailbreak and mental breakdown of numerous "inmates."

The Stanford Prison Experiment: A Simulation Study of the Psychology of Imprisonment

Get ahold of Flock

<Foil helmet on>

Pentagon sets its sights on social networking websites, aka MySpace and FaceBook.

 </Foil helmet off>