It was properly documented. It was an entirely understandable mistake, if you assume the person who made it was so goddamn stupid he felt he had to mess with the guts of OpenSSL.
I'm pretty sure it was getting the memory off the stack, not the heap. OSes already do what you suggest when you allocate memory on the heap that was used by another process.
Apparently, OpenSSL was using uninitialized memory as a source of randomness. This made valgrind complain about the program, and some enterprising programmer decided to fix it by clearing the memory before use.
After all, someone closed a 25-year bug... how many hidden bugs will remain that way in os/2 warp? windows 95? other proprietary systems? Er, this bug was in current versions, too, you know.
That would require completely new x86 chips. You can't just re-used desktop processors for embedded systems, there's far too much support circuitry required. Embedded processors need to be highly integrated, with lots of circuitry on-chip.
And if you need new chips for that, why use x86 for those when you can use ARM?
There's also being able to aim up/down, I'd say that was pretty major. "Major"? That's nothing by the tiniest of implementation details! If that's what's considered a "major" change these days, it's no wonder gaming is in the sorry state it is.
To sum up what everyone's said: "RAW" does not mean "raw RGB". It means "raw data right off the image sensor". This data needs quite a bit of post-processing before it becomes anything like RGB data.
And that's not all. You don't get RGB data out of a CCD sensor. You get a single 8-bit (or higher for fancier ones) value per pixel. There's a filter grid on top of the sensors so that some pixels capture red, some green, and some blue. You have to interpolate the colours from your knowledge of this grid.
Oh, and of course those aren't pure R, G and B either, just approximate. There's quite a bit of mixing going on between the channels, so you have to compensate for that. And then you have to do white balance compensation. And noise reduction. And so on.
Why does a takedown notice get more respect than the site owner? Because that's what the law says. When a host is served a DMCA takedown notice, they respond. Then the affected party can file a counter-notice to have the site put back up.
After that, it's up to the courts, if either party wants to take it that far.
No, he was doing a shitty job ofg quoting the parent poster. You don't quote people by suddenly starting to copy what they said in mid-sentence with no other marker than suddenly using italics, which is totally ambiguous in meaning.
coÂinÂciÂdenÂtal
Audio Help/koÊSËOEÉnsÉËdÉntl/ Pronunciation Key - Show Spelled Pronunciation[koh-in-si-den-tl] Pronunciation Key - Show IPA Pronunciation â"adjective 1. happening by or resulting from coincidence; by chance: a coincidental meeting. 2. existing or occurring at the same time. [Origin: 1790â"1800; coincident + -al1]
Slashdot Mirror
It was properly documented. It was an entirely understandable mistake, if you assume the person who made it was so goddamn stupid he felt he had to mess with the guts of OpenSSL.
OpenSSH is hardly "every cryptography program".
I'm pretty sure it was getting the memory off the stack, not the heap. OSes already do what you suggest when you allocate memory on the heap that was used by another process.
Apparently, OpenSSL was using uninitialized memory as a source of randomness. This made valgrind complain about the program, and some enterprising programmer decided to fix it by clearing the memory before use.
Perhaps they didn't feel like doing the "no, it's supposed to work like that, you're wrong" dance.
Samba cared enough to implement a workaround.
Except that the bug had been triggered many times before, seeing as how Samba had code in place to work around it.
No, they have blanket policies against illegal content.
That would require completely new x86 chips. You can't just re-used desktop processors for embedded systems, there's far too much support circuitry required. Embedded processors need to be highly integrated, with lots of circuitry on-chip.
And if you need new chips for that, why use x86 for those when you can use ARM?
To sum up what everyone's said: "RAW" does not mean "raw RGB". It means "raw data right off the image sensor". This data needs quite a bit of post-processing before it becomes anything like RGB data.
And that's not all. You don't get RGB data out of a CCD sensor. You get a single 8-bit (or higher for fancier ones) value per pixel. There's a filter grid on top of the sensors so that some pixels capture red, some green, and some blue. You have to interpolate the colours from your knowledge of this grid.
Oh, and of course those aren't pure R, G and B either, just approximate. There's quite a bit of mixing going on between the channels, so you have to compensate for that. And then you have to do white balance compensation. And noise reduction. And so on.
Considering that the reason this works is mostly because features are intentionally disabled by Canon, no, I don't see that happening any time soon.
Even if you hate all platforms, that doesn't mean you can't think one sucks less than another, or that one sucks less than all others.
After that, it's up to the courts, if either party wants to take it that far.
The point is that humans run on solar power, too.
No, he was doing a shitty job ofg quoting the parent poster. You don't quote people by suddenly starting to copy what they said in mid-sentence with no other marker than suddenly using italics, which is totally ambiguous in meaning.
POSIX, that thing that Linux isn't?
I thought the US had laws against cruel and unusual punishments.
(Good work with the unicode, Slashdot!)
coÂinÂciÂdenÂtal /koÊSËOEÉnsÉËdÉntl/ Pronunciation Key - Show Spelled Pronunciation[koh-in-si-den-tl] Pronunciation Key - Show IPA Pronunciation
Audio Help
â"adjective
1. happening by or resulting from coincidence; by chance: a coincidental meeting.
2. existing or occurring at the same time.
[Origin: 1790â"1800; coincident + -al1]
http://dictionary.reference.com/browse/coincidentally