From: James A. Donald [EMAIL PROTECTED]
...
If the optimizer ever optimizes away a write to volatile
memory, device drivers will fail. Most device drivers are
written in C. If anyone ever produces a C compiler in which
volatile does not do what we want, not only are they out of
spec, but smoke
At 8:40 PM -0800 11/7/02, Peter Gutmann wrote:
It's worth reading the full thread on vuln-dev, which starts at
http://online.securityfocus.com/archive/82/297827/2002-10-29/2002-11-04/0.
This discusses lots of fool-the-compiler tricks, along with rebuttals
on why they could fail.
In that
Here's the URL, I haven't noticed it in this message
thread yet:
http://www.artbell.com/letters88.html
-- gbn
On Sat, Nov 09, 2002 at 08:32:18PM -0500, Tyler Durden wrote:
The subject line says it all, if one remembers Variola's clever dare.
As far as I'm concerned, this big
At 08:32 PM 11/9/02 -0500, Tyler Durden wrote:
So I'm still playing with the idea of a publically-accessible document
that
outlines the strategies, technologies, aims and requirements for
somehow
uploading images and data to public repositorioes.
Such a document should enumerate the threat model
The subject line says it all, if one remembers Variola's clever dare.
As far as I'm concerned, this big brother bullshit should work two ways: any
tyrrany should expect that any public actions will make it onto the net
somewhere. Of course, one day they'll probably begin a set of countermoves,
