* Edmund GRIMLEY EVANS ([EMAIL PROTECTED]) [000328 10:52]:
> However, a copy of the passphrase may still be left in your swap
> partition. (I think that only a process running as root can prevent
> memory from being written to swap, and even then only on some systems.
> If this is incorrect, perhaps someone can explain the true situation.)
This really depends on the system you're running on. For most unices this is
true, tho with ACL's this will probably change.
I would vote in flavour of allowing mutt to be run as root, only to lock the
memory blocks, then su to the user fast as hell. I'm not saying this is the
right way for all users, but it might be a desirable feature for some. Thing of
for example a single user workstation, where nobody else has access, so
running setuid isn't really a problem. In such a situation it'd be much worse
to write to swap than to have a exploitable prog running.
Just my $0.02
Terje
--
Tuj uh yaau fudj å buiu qdthu fuhieduhi ahofjuhju cubtydwuh.
Uh yaau tujju qbj tuj rulyiuj tk jhudwuh veh å yddiu qj cqd cå rhkau
ijuhauhu shofje?
