From: David Christensen <dpchrist@holgerdanske.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] linux luks automatic boot with keyfile (INSECURE)
Date: Thu, 24 May 2012 23:20:18 -0700 [thread overview]
Message-ID: <4FBF24A2.9060907@holgerdanske.com> (raw)
In-Reply-To: <CAE2+g+LPHRmsLcsaodbfFHAYs8U0WjU_354FRHqw2WYOa4t_jw@mail.gmail.com>
On 05/24/2012 07:29 PM, Nuno Reis wrote:
> I would like to ask you about the best choice to have one or two luks
> encrypted partitions to boot automatically between reboots without me to
> enter a pass-phrase.
> I've made this already, but the way i'm doing it seems to be not very
> secure since the keyfile is referenced in /etc/crypttab and the keyfile and
> /etc/crypttab both reside on an unencrypted partition. If someone clones my
> HDD and connect it to some other system will easily be able to mount the
> unencrypted partitions and find the keyfile reference on /etc/crypttab to
> get the keyfile and unencrypt the protected partitions right?
> So basically my problem is that i want to sell a linux server with some
> software i've developed to a datacenter (as an appliance), but i don't want
> them to get to my software easily and i can't have a password prompt
> between reboots also.
> Can you point me out what you think would be the best solution for me?
If you want to protect software, perhaps you should consider a software
protection dongle:
http://en.wikipedia.org/wiki/Software_protection_dongle
HTH,
David
next prev parent reply other threads:[~2012-05-25 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 2:29 [dm-crypt] linux luks automatic boot with keyfile (INSECURE) Nuno Reis
2012-05-25 6:20 ` David Christensen [this message]
2012-05-25 8:11 ` Arno Wagner
2012-05-25 9:37 ` Hp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FBF24A2.9060907@holgerdanske.com \
--to=dpchrist@holgerdanske.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox