mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-03-22 14:39:24 -05:00
Actually, VirtualLock() looks better as \cw{} not \c{}.
[originally from svn r1826]
This commit is contained in:
parent
0011fa6dda
commit
1601559c8c
18
doc/faq.but
18
doc/faq.but
@ -1,4 +1,4 @@
|
|||||||
\versionid $Id: faq.but,v 1.31 2002/08/09 09:11:09 simon Exp $
|
\versionid $Id: faq.but,v 1.32 2002/08/09 09:14:04 simon Exp $
|
||||||
|
|
||||||
\A{faq} PuTTY FAQ
|
\A{faq} PuTTY FAQ
|
||||||
|
|
||||||
@ -795,15 +795,15 @@ all. For this reason we now believe PuTTY's DSA implementation is
|
|||||||
probably OK. However, if you have the choice, we still recommend you
|
probably OK. However, if you have the choice, we still recommend you
|
||||||
use RSA instead.
|
use RSA instead.
|
||||||
|
|
||||||
\S{faq-virtuallock}{Question} Couldn't Pageant use \c{VirtualLock()}
|
\S{faq-virtuallock}{Question} Couldn't Pageant use
|
||||||
to stop private keys being written to disk?
|
\cw{VirtualLock()} to stop private keys being written to disk?
|
||||||
|
|
||||||
Unfortunately not. The \c{VirtualLock()} function in the Windows API
|
Unfortunately not. The \cw{VirtualLock()} function in the Windows
|
||||||
doesn't do a proper job: it may prevent small pieces of a process's
|
API doesn't do a proper job: it may prevent small pieces of a
|
||||||
memory from being paged to disk while the process is running, but it
|
process's memory from being paged to disk while the process is
|
||||||
doesn't stop the process's memory as a whole from being swapped
|
running, but it doesn't stop the process's memory as a whole from
|
||||||
completely out to disk when the process is long-term inactive. And
|
being swapped completely out to disk when the process is long-term
|
||||||
Pageant spends most of its time inactive.
|
inactive. And Pageant spends most of its time inactive.
|
||||||
|
|
||||||
\H{faq-admin} Administrative questions
|
\H{faq-admin} Administrative questions
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user