I have recently read the news about Google Chrome Buffer Overflow vulnerability (see this link). Admittedly, I was ignorant enough not to understand how a buffer overflow can cause severe security breaches! Wikipedia came to the rescue, as well as some research into the topic of Assembly-language programming. At last I can understand how SEVERE such an attack could be!
You can dig for it too ;-)
check the Wikipedia article,
http://en.wikipedia.org/wiki/Buffer_overflow
and the excellent book of Programming from the Ground Up, for much better understanding of Assembly:
http://savannah.nongnu.org/projects/pgubook/
Enjoy!
Popular Posts
-
Recently I needed to add a header/footer to an existing PDF file. With some help from this link, I figured it out: http://coding.derkeiler.c...
-
Sometimes you have to deal with the .Net framework in a way or another. I was forced to use a .Net C# closed-source library. And that librar...
-
eBox 2300SX http://www.murga-linux.com/puppy/viewtopic.php?t=21864 eBox 2300 http://www.murga-linux.com/puppy/viewtopic.php?search_id=210596...
-
Today I tried to compile and install the WFDB tools from the PhysioToolkit ( PhysioNet ) on my Debian Squeeze system. I am documen...
-
To print multiple pages/sheet, you'll need the `pdfjam' package installed. Then, $pdfnup --nup 1x2 input.pdf
Saturday, September 27, 2008
Wednesday, September 3, 2008
Subscribe to:
Comments (Atom)