gpg: failed to create temporary file '/var/lib/lurker/.#lk0x5695f100.hantslug.org.uk.25724': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: Signature made Mon Sep 5 03:33:13 2011 BST
gpg: using DSA key 2099B64CBF15490B
gpg: Can't check signature: No public key
Hi Mike,
On Sun, Sep 04, 2011 at 09:43:53AM +0100, Mike Austin wrote:
> Those of you concerned about loss of a computer or Smartphone should visit
>
> http://preyproject.com/download
I've been thinking about this, but the difficulty is that I kind of
want to continue using full disk encryption. Expecting a thief to
know how to log in to Linux is already a bit unlikely, before you
even add the encryption. I'm thinking it's more likely that they
would know how to wipe the SSD and install Windows, or just sell it
as-is down the pub.
What do people do to ensure that Prey can be run even while using
full disk encryption?
I was thinking it would be nice if dm-crypt would have a password
timeout so that e.g. after 30 seconds it boots into something else.
Even then, the trouble is I'd have to install a minimal Linux
environment on the alternate boot just to be confident that it gets
online, webcam works, etc. This sounds like a lot of work.
I don't really want to start only encrypting certain directories
(e.g. /home); I don't trust *myself* to never put sensitive info
outside these directories, so if I was in charge of desktop support
at a larger company I would certainly never trust employees to do
the right thing in this regard.
Maybe it comes down to how paranoid you are. It's just that dm-crypt
works really nicely these days so it's hard to justify not using it
on mobile devices.
It would be interesting if the BIOS could do all the stuff that Prey
does!
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
