News for hackers. Stuff that matters.
Re:Understanding the LZ4 Memory Corruption Vulnerability: Yo... by nkurz on Saturday June 28, 2014 @01:40PM (#7958756)

  It's Just Not Big Enough
  The claim that 64bit platforms are not exploitable is 
  incorrect. This is the same mindset that created today's 
  LZO/LZ4 vulnerability. "No one will ever have that much 
  RAM to cause a 32bit integer overflow!". Well, today we 
  do. If this bug would have persisted and propagated 
  further, surely 64bit architectures would be effected in 
  the not-so-near future. 
Worrying that RAM sizes will exceed 64-bit addressability hasn't been one of my worries. 2^64 is about 70,000 Petabytes. Of course, it wasn't too long ago when a Petabyte seemed unattainable, and not too long before that that a Gigabyte seemed giant, and even a Megabyte once seemed almost limitless. Am I just being short sighted?
Re:Understanding the LZ4 Memory Corruption Vulnerability: Yo... by Tractor4973 on Saturday June 28, 2014 @01:56PM (#7958798)
Of course, this argument is totally nuts. 2^64 of RAM is not accessible, period. It's ludicrous to pretend that a code delivered today should take into consideration a potential issue that might happen in 30 years from now. Frankly, you expect the code to no longer be updated that long and still be used ??
Re:Understanding the LZ4 Memory Corruption Vulnerability: Yo... by OMGWTF on Saturday June 28, 2014 @03:25PM (#7959045)
Well, if a fix is possible without much hassle, it should be implemented. But it's crazy to raise as much attention as in this case.