Microsoft kills more code-signing certs to stop Flame-like attacks
|
|
|
Comments (4)
This is what the future looks like once we all have UEFI secure boot. How do you update a vulnerable MS key on such a system?
Through M$ obviously. Feel safer now? :D
When it takes 20 minutes on a fat pipe to do the first Windows update, but only 30 seconds for a remote compromise?
That's the result of security as an afterthought.
That's the result of security as an afterthought.
There is only one secure thing about Windows: You are secure in the knowledge that Windows is insecure.
I think UEFI certificates are simply a method of control to try to stop the slow erosion of the Microsoft Empire that is now becoming very visible.
Try this:
http://fossforce.com/2012/07/windows-era-hand/
I think UEFI certificates are simply a method of control to try to stop the slow erosion of the Microsoft Empire that is now becoming very visible.
Try this:
http://fossforce.com/2012/07/windows-era-hand/
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post
