[EMAIL PROTECTED] (Peter Gutmann) writes:
Which operating systems leak memory between processes in this way?
Win32 via ReadProcessMemory.
The documentation for the function says it will check read access
permissions. Isn't this permission check done properly? I.e.,
disallow memory reads
Simon Josefsson [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] (Peter Gutmann) writes:
Which operating systems leak memory between processes in this way?
Win32 via ReadProcessMemory.
The documentation for the function says it will check read access
permissions. Isn't this permission check done
1) This topic must be taken seriously. A standard technique
for attacking a system is to request a bunch of memory or
disk space, leave it uninitialized, and see what you've got.
2) As regards the volatile keyword, I agree with Perry.
The two punchlines are:
if, for example, gcc did not honor
John S. Denker [EMAIL PROTECTED] writes:
1) This topic must be taken seriously. A standard technique
for attacking a system is to request a bunch of memory or
disk space, leave it uninitialized, and see what you've got.
I find that this thread doesn't discuss the threat model behind
