diff options
| author | Werner Koch <wk@gnupg.org> | 1999-08-31 17:30:12 +0200 |
|---|---|---|
| committer | Werner Koch <wk@gnupg.org> | 1999-08-31 17:30:12 +0200 |
| commit | 88a916cdd40e43312ffcde6bb1c157fe1c122f74 (patch) | |
| tree | d5298986a0bad2aff797fd981f99fb3cb6f99ba9 /THOUGHTS | |
| parent | See ChangeLog: Mon Aug 30 20:38:33 CEST 1999 Werner Koch (diff) | |
| download | gnupg2-88a916cdd40e43312ffcde6bb1c157fe1c122f74.tar.xz gnupg2-88a916cdd40e43312ffcde6bb1c157fe1c122f74.zip | |
See ChangeLog: Tue Aug 31 17:20:44 CEST 1999 Werner Koch
Diffstat (limited to 'THOUGHTS')
| -rw-r--r-- | THOUGHTS | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -23,7 +23,7 @@ conditional. more secure than swapping out to the swap disk? I don't believe so because if an attacker has access to the physical box (and he needs this to look at the swap area) he can also - leave a trojan horse which is far more easier than to analyze + leave a Trojan horse which is far more easier than to analyze memory dumps. Question: Is it possible that a Unix pages an old (left over by some other process) swap page in for another process - this should be considered a serious design |