[12000] in cryptography@c2.net mail archive

home help back first fref pref prev next nref lref last post

Re: Did you *really* zeroize that key?

daemon@ATHENA.MIT.EDU (Rich Salz)
Thu Nov 7 13:29:52 2002

Date: Wed, 6 Nov 2002 23:21:02 -0500 (EST)
From: Rich Salz <rsalz@datapower.com>
To: Marc Branchaud <marcnarc@rsasecurity.com>
Cc: "cryptography@wasabisystems.com" <cryptography@wasabisystems.com>
In-Reply-To: <3DC9A3D6.2010601@rsasecurity.com>

Probably moving out of the domain of the crypto list.

> 	volatile char *foo;

volatile, like const, is a storage-class modifier.  As written, it
means a pointer to memory that is volatile; this means, in particular,
that you can't optimize away dereferences.  If you wrote
        char * volatile foo;
That means that foo itself is volatile, and you must fetch it from
memory whenever you want its value.

You might find the cdecl program useful...

    ; cdecl
    Type `help' or `?' for help
    cdecl> explain volatile void* vp
    declare vp as pointer to volatile void
    cdecl> explain void * volatile vp
    declare vp as volatile pointer to void
    cdecl> explain volatile void * volatile vp
    declare vp as volatile pointer to volatile void



---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@wasabisystems.com

home help back first fref pref prev next nref lref last post