11–20 of 82 posts
Earlier quoted context omitted.
The other thing I wonder about is that in 2040, will we be still worrying about buffer overflows?
I really doubt that we'll be using programming environments where memory corruption is possible in 2040.
What's amazing about this bug is that at every step you learn something that makes Pinkie Pie more terrifying while simultaneously making the Chrome security model sound more and more forbidding.
---
In an upcoming post, we’ll explain the details of Sergey Glazunov’s exploit, which relied on roughly 10 distinct bugs. While these issues are already fixed in Chrome, some of them impact a much broader array of products from a range of companies. So, we won’t be posting that part until we’re comfortable that all affected products have had an adequate time to push fixes to their users.
Earlier quoted context omitted.
I really doubt that we'll be using programming environments where memory corruption is possible in 2040.
someone's gotta write the kernels though, I can't think of any way to write kernels or compilers where memory corruption is impossible.
Earlier quoted context omitted.
The other thing I wonder about is that in 2040, will we be still worrying about buffer overflows?
I really doubt that we'll be using programming environments where memory corruption is possible in 2040.
http://sip.cs.princeton.edu/pub/memerr.pdf
Neat hack :)
So crazy. I wonder how long it took to come up with that attack? There must have been a ton of dead ends along the way.
Source: http://arstechnica.com/business/2012/03/googles-chrome-brows...
This really takes you into the mind of a hacker(the malicious kind). Judging from what I saw it seems they combine a ton of small exploits to produce a major security breach. The amount of understanding of the underlying system you need to have in order to put these exploits together is mind boggling. What do we do against people like this?
Pay them to find the bugs!
Earlier quoted context omitted.
I really doubt that we'll be using programming environments where memory corruption is possible in 2040.
someone's gotta write the kernels though, I can't think of any way to write kernels or compilers where memory corruption is impossible.
There is a version of the L4 microkernel that has been formally verified which should prevent memory corruption in kernel space, but I don't know the exact details.
This of course won't prevent corruption due to physical sources, such as radiation, but with physical access to a machine you will always be able to gain access.
If you don't have a young girl you might not appreciate the link between "Pinkie Pie" and "Pwnie": http://mlp.wikia.com/wiki/Pinkie_Pie
If you don't have a young girl you might not appreciate the link between "Pinkie Pie" and "Pwnie": http://mlp.wikia.com/wiki/Pinkie_Pie
Considering that he is a teenage hacker, it's likely that he is a Brony himself.