Messages in this thread | | | Subject | Re: mlock(1) | From | Nigel Cunningham <> | Date | Mon, 27 Sep 2004 20:32:43 +1000 |
| |
Hi.
On Mon, 2004-09-27 at 16:16, Stefan Seyfried wrote: > Andrea Arcangeli wrote: > > > random keys are exactly fine, but only for the swap usage on a desktop > > machine (the one I mentioned above, where the user will not be asked for > > a password), but it's not ok for suspend/resume, suspend/resume needs > > a regular password asked to the user both at suspend time and at resume > > time. > > Why not ask on every boot? (and yes, the passphrase could be stored on a > fixed disk location - hashed with a function of sufficient complexity > and number of bits, just to warn the user if he does a typo, couldn't > it?). If suspend is working, you basically never reboot. So why ask on > suspend _and_ resume? This also solves the "suspend on lid close" issue. > > And a resume is - in the beginning - a boot, so just ask early enough > (maybe the bootloader could do this?) > > I'm not a crypto expert at all, just thinking loud...
I loved Andrea's compare-the-checksum idea, but don't see why the passphrase is needed both times either. Then again I have zero experience with encryption. In fact, I care so much about security that I don't have a root password and have sudo without a password :>
Regards,
Nigel -- Nigel Cunningham Pastoral Worker Christian Reformed Church of Tuggeranong PO Box 1004, Tuggeranong, ACT 2901
Many today claim to be tolerant. True tolerance, however, can cope with others being intolerant.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |