Microsoft's Urgent Patch Precedes Black Hat Session
Julie188 writes "Mystery solved! Microsoft's latest emergency out-of-band patch was weird beyond belief. A notice was sent to journalists and researchers late Friday evening that the patch was coming Tuesday, but Microsoft refused to explain the flaw and even put a cone of silence around researchers who would have otherwise talked about it. But finally, one researcher broke ranks and explained that the patch was caused by a flaw introduced in Microsoft's own development tools. This flaw was also the source of the emergency ActiveX patch, which took about 18 months to complete and which supposedly fixed the problem by turning off ActiveX (setting a 'killbit' on the control). Researchers at Black Hat on Wednesday will be demonstrating how to override the killbit controls and get access to vulnerabilities supposedly stopped with a killbit. What's really scary is that Microsoft has issued 175 killbits fixes so far."
There are still people that think ActiveX is a gift to humanity.
damned if they do damned if they dont?
If you mod me down, I will become more powerful than you can imagine....
Microsoft refused to explain the flaw and even put a cone of silence around researchers
Those suck. My dog had to wear one of them for a week. Didn't shut him up but it sure stopped him from licking what used to be his balls.
My work here is dung.
I've always been baffled by Microsoft marketing's insistence that ActiveX is pronouced "active" with the "X" silent. I've never met anyone who didn't pronounce the technology "Active-X".
I also didn't like how ActiveX morphed from a special browser-only technology into a synonym for COM and then into a replacement for OLE. At least now we've got .NET which promises to rid us of C++ once and for all.
Whoever thought making C/C++ an implementation language for anything as complicated as an OS ought to be shot. The number of possible vulnerabilities is through the roof, as this latest patch shows.
Didn't Shaun of the Dead do that first?
To make a patch that simply turned off ActiveX? I better be misreading this...
After years of not using a signature, I am going to make one to say the following: Fuck Beta
Instead of releasing a KillBit patch, why not releasing once and for all a Kill ActiveX patch ? The Web as yould be a safer place.
1. Be told of critical flaw by multiple, repeatable accounts and deny everything as a "paranoid fantasy"
2. Secretly prepare emergency patch and bury it in driver update patches
3. ???
4. PROFIT!!!
When I hear about killbits, killbill comes in my mind. I don't know why though...
Until the skies turn blue...
Until the air of freedom strikes us...
So in this case the "band" is simply the normal monthly patch-tuesday update. Being outside that makes it out-of-band. Why does a band have to mean an entirely different medium of communication?
In any case, you can't fight it. I've heard this usage enough that it's part of standard techno-babble.
AccountKiller
After a while, these sequels all seem the same to me. Pass the popcorn please.
Say hello to my little sig.
The thing about Active X is that is just a way to put an object oriented wrapper around a DLL. So really, its just a DLL.
The problem with DLLs is that they are good for process re-use on a desktop but not the kind of thing you want to be shoving into a browser. However, if Microsoft closed off Active X entirely in browsers, they would break Flash and third party OpenGL and movie plugins... and probably would wind up getting ripped for it.
The thing to keep in mind is that Firefox and other browsers that allow for DLLs to be loaded as plugins are going to have these problems as well. It's just that, there are less firefox plugins than there are activex controls out there, so the universe of the problem is smaller.
This is my sig.
"But finally, one researcher broke ranks and explained that the patch was caused by a flaw introduced in Microsoft's own development tools. This flaw was also the source of the emergency ActiveX patch." Or one could say that Microsoft was making a mountain out of a molehill. So what else was in that patch? I have a right to question Microsoft's antics . After all, they made me paranoid.
I'm not going to get into why having automatic updates on is generally a bad idea, that subject has already been beaten to death here.
/quiet /norestart
WindowsXP-KB972260-x86-ENU.exe
That is the one for XP with IE6, the filenames are different for the other flavors. The list of all of the different patches is at:
http://www.microsoft.com/technet/security/bulletin/ms09-034.mspx/
I've got a Powerbook G4, running 10.5.x... which is still a fairly powerful machine, right? Well, yes, but... increasing numbers of software packages won't run on anything but Intel-based Macs, or alternatively, have features crippled when running on PPC Macs. So even though there's nothing wrong with the machine, and it still has sufficient horsepower to do just about anything... Steve is going to force me to buy a new one if I want to run modern software. Yay, Mac.
You can't be serious - nearly every OS these days is written in C (with a few bits of assembler at the core). And the one viable alternative, C++, was pretty much confined to BeOS. Do think everyone just left their thinking caps at home the day they decided which language to write in? Fair swig of the whiskey. C was pretty much invented as a means of writing systems software. And you do realize that .NET is really just ActiveX by another name, smelling just as 'sweet'...
Every MS patch allows a /norestart option, but sometimes the software they patch is memory resident (especially IE based stuff), so rebooting afterward makes sense.
Of course being so close to the metal means that its easier for programmers to screw up... but I'm not sure C# will be used to build the base of an OS anytime soon. You'd almost have to make the CLR the OS... which while an interesting idea not one I think we'd see soon.
Wasn't Longhorn (Vista) supposed to more or less be this?
today is spelling optional day.
Plugins are DLLs... NSAPI I though was for servers side DLLs, like ISAPI is sort of a clone of... in any case, here's the mozilla doc for the plug in run time model.
https://developer.mozilla.org/en/Gecko_Plugin_API_Reference/Plug-in_Basics#Understanding_the_Runtime_Model
Note that a plug in is a DLL that uses the same thread as the browser... just like Active X.
This is my sig.
I just installed using the automatic updates thing (prompt before install) and I was not asked to reboot.
Yeah. I'm pissed off because my 4-or-so-year-old dual 2.7Ghz G5 tower is becoming less and less viable - even though it's still a fast, powerful machine, even by today's standards.
MS wanted Active-X to allow for web domination because when sites used it, Netscape and other OSes would no longer be able to access the sites. So, many sites did use it and everyone needed IE, but then security problems, Flash, Java, Javascript and other tools came around and who now would add Active-X to a general-user web site? Remaining support for it comes from companies that use web apps. Good luck with those rewrites.
Microsoft has issued 175 killbits fixes so far.
So, how many kilobytes of killbits is that?
Returned Peace Corps IT Volunteer
Worse, there are still people who thinks something good can come out of the company who still doesn't kill the technology and even tries to photocopy it to open source, free operating systems.
We all know who they are...
All PPC here except other family members have their Intel macs. I use from G4 Mini up to G5 Quad so I had pretty good time to think about it.
It is not Apple or SJobs fault that IBM and Motorola, on Desktop CPUs, never cared enough. They don't have that culture to begin with. IBM is back to its roots, only making mainframe, enterprise CPUs and CUSTOM built Console CPUs which 2 giants like Microsoft and Sony can provide significant input for their needs. Look to MS, they could make IBM actually care about their suggestions and they could truly work with them. See the xbox 360 success compared to the earlier joke.
Compile open source software on powerpc and intel, both OS X and see the difference. Intel has all the "cool stuff", they somehow made developers code and support their (backwards) MMX and SSE while we get surprised when Altivec used by some rare and great open source developers. Mplayer for example.
The thing to blame SJobs is, he showed "universal binary" as something very easy, just click something and it compiles. It is NOT the case except for very simple applications or applications having their own frameworks (like Opera). Obviously, you can compile "Hello World" for MC68000 too, with single click but when libraries, frameworks and especially stuff like CUDA, OpenCL gets involved, that magic is instantly gone.
The Framework or Library, having millions of lines, millions of manhours doesn't run on anything other than x86. Now what to do?
It is mostly the entire deal for Snow Leopard and another reason is, Intel 64bit is a huge hack requiring "pure 64bit" to run better. PowerPC which was designed with 32/64bit in mind from ground doesn't have that issue and in fact, needless pure 64bit on PPC will run slower in most cases.
My PC belongs to ME. I woke up this morning and MS had rebooted it. I was running a process overnight that was important to me. Now MS has one less auto-update user. Is that what you intended, MS?
How many people are still using an OS that's 9 years old? Most folks would have upgraded to a newer version at some point or if they were too cheap to spread for the OS they would also probably be too cheap to upgrade their software and hardware, meaning everything still works anyway. Windows 2000 has about a 1% market share. Why would any developer go out of their way to ensure compatibility for it? I wouldn't. Hell, I'm in IT and I don't even know anyone that still uses W2K.
OS X was released 11 months after Windows 2000. It's doubtful you would find apps in today's software stores touting compatibility with Windows 98 or Windows ME as that is a closer comparison to Mac OS 9. If your apps and hardware are older than that, it's unlikely you would be upgrading to OS X to begin with. If you upgraded your hardware, you already have OS X. Even most home users upgrade every 4-5 years. They would be forced to due to hardware failure at some point.
When it comes to cost, there really isn't much of a comparison. OS X comes with a full suite of applications from iLife including iPhoto (photo editing), iWeb (web site design), iDVD, as well as support for MPEG-2, H.264, and AAC out of the box. There is no 'basic' version of OS X. You get everything in a single package. It also includes a full development suite for OS X (XCode).
Windows 7 comes with Paint, but no MPEG-2, H.264, or AAC in the basic editions and no MPEG-2/H.264/AAC support at all in previous versions.
If you want to develop for Windows it will cost you another $299 for the MS offering (Visual Studio).
The full Monty for a Windows (Ultimate Edition) costs $100 more than the 'regular' release of OS X. On top of that, if you use a pay antivirus like McAfee (the free flavors seem just as dangerous as a virus these days), you're also paying yearly subscriptions for updated DATs every year.
Lets do the math:
Windows 7 Ultimate: $219
McAfee (single pc): $50 (1 year subscription for dats)
Web Design: $50 (for a cheap one like CoffeeCup..MS's own offering is $300)
DVD Software: $80
Visual Studio: $199
Total: $598
OS X with iLife includes all of the above.
Cost for OS X/iLife $169
Now if you had to buy Windows for your home, which arguably will have more than 1 PC, you can do so for the Mac for $229 (5 license).
Windows will cost you 5 times the base cost just for the OS alone if you have a multi-pc home, which is becoming the norm.
A 5 license package from MS for the OS costs alone: ($229 x 5 = $1145).
Can't they just take names and watch hackers until they break a law and then throw them in the clink? How hard would it be?
no, it doesn't since Vista