This came up when reporting a couple IIS errors on an Exchange server today. I was investigating another problem so haven't looked back at the logs to figure out what actually happened (probably unlikely to be identifiable anyways, but initial guess is NLB related). It's not like this message is uncommon, but it provided a well-timed bit of humor to break up the searching.
Today was a bit of a cleaning day in the barn, and I glanced through a disk case and noticed this set of Windows NT 3.5 floppies.
Today, Microsoft announced what they're calling Windows Principles. It's rather interesting, although I'm guessing by "commercially reasonable terms" they mean it won't be free for community-developed software to use. The whole saying they won't change the licensing terms to OEMs based on whether they allow non-MS systems will be more interesting on the economic side. I'm curious what it will do to the cost of the low-end PC market.
Vulnerability in DHCP Client Service Could Allow Remote Code Execution. That's a fun one seeing as almost everyone uses DHCP so people don't have to manually reconfigure to switch networks. Now not only can you redirect and capture all of someones traffic by issuing responses, but run code so they're still yours when they leave. At least the same switch protections that prevent rogue DHCP servers should prevent this from working.
Aaron Margosis posted an interesting thought on Anti-Virus vs Non-Admin (LUA). Basically with what's out there and the assumptions it makes, it's currently better to just run LUA (not as an Administrator) without any anti-virus or anti-malware than to run as admin because the protection software breaks otherwise.
I didn't realize there was such broken "security" software for Windows. They didn't name names in the articles though. Does anyone know which they are so I can avoid them when others ask me?
Copyright ©2000-2008 Jeremy Mooney (jeremy-at-qux-dot-net)
