From: Peter Korsgaard <peter@korsgaard.com>
To: Zvi Vered <veredz72@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] LKUS in buildroot 2023.02.9
Date: Tue, 30 Jan 2024 23:03:51 +0100 [thread overview]
Message-ID: <87il3azdfc.fsf@48ers.dk> (raw)
In-Reply-To: <CABRndgy7KsqtSyzJJaw9r6a7c9atEpPQpbbJgGn2qY=yi=nLFg@mail.gmail.com> (Zvi Vered's message of "Tue, 30 Jan 2024 09:54:53 +0200")
>>>>> "Zvi" == Zvi Vered <veredz72@gmail.com> writes:
> Hello,
> I'm booting an x86 Intel CPU using Linux 4.9.20 (32 bits) and buildroot
> 2023.02.9
> I consider using LKUS in order to encrypt the disk.
> Is it a wise decision ?
LKUS? Do you mean LUKS (Linux Unified Key Setup)? LUKS is good (but is
just a standard for describing the encryption meta data).
Any specific reason for using such an old Linux kernel version?
> The motivation: If someone will steal the disk, it will be difficult to
> copy its contents.
> I can not use hardware encryption because I cannot replace the disk.
Like always with encryption, the difficult part is handling the
encryption key - Especially if the system is to boot unattended.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-01-30 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 7:54 [Buildroot] LKUS in buildroot 2023.02.9 Zvi Vered
2024-01-30 22:03 ` Peter Korsgaard [this message]
2024-01-31 7:31 ` Zvi Vered
2024-01-31 8:14 ` Peter Korsgaard
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=87il3azdfc.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=veredz72@gmail.com \
/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