From: Milan Broz <gmazyland@gmail.com>
To: Fabian Stargalla <fabestah@gmail.com>, cryptsetup@lists.linux.dev
Subject: Re: How to use Serpent
Date: Tue, 29 Aug 2023 09:01:59 +0200 [thread overview]
Message-ID: <159b42fe-d616-4a4f-8fbe-cff5067a57f5@gmail.com> (raw)
In-Reply-To: <CAMEBZxWhAmwuJqpvtk0mh5vceEp_9AEs46DKC94vGQkrqW6uCg@mail.gmail.com>
On 8/28/23 01:37, Fabian Stargalla wrote:
> I would like to seek advice from someone who is familiar with the
> Serpent cipher, encryption and cryptsetup in general.
> Currently, I'm planning my new Arch installation with a BTRFS
> filesystem that is encrypted using cryptsetup and LUKS, and I'm
> finding little to no information on how to properly use the Serpent
> cipher for system encryption, as well as for encrypting hard drives
> solely for data storage, and for a swap partition to enable
> hibernation support.
> From what I've read and understood so far, it would be best to use
> Serpent for my system encryption in the same way AES is used by
> default with LUKS, that would be serpent-xts-plain64, but I'm not 100%
> sure and can't verify it any other way than to ask here.
> Furthermore, I would also like to know if the XTS mode with plain64 is
> also appropriate and works well for my swap partition and my data
> storage drives/partitions?
Usually if you need to ask these questions, then just use defaults.
Anyway, Serpent works with LUKS without problem, all you need to do
is use --cipher serpent-xts-plain64 during format (and enable Serpent
in kernel). XTS mode with plain64 IV is appropriate (and the best option)
here.
But as there is no hw optimization, you will get significantly slower
encryption compared to AES-NI (check output of "cryptsetup benchmark"
it measures Serpent by default, see 512bit key as it is default for XTS).
> Just in case someone says I should just be using default AES (like in
> one thread on the Arch forum):
> My primary concern is the higher level of security that Serpent
> offers, which is why I prefer it over the default AES encryption. That
> also means that speed is completely irrelevant to me, as long as it
> remains within a bearable range.
It is also about implementation issues. I highly doubt sw implementation
of Serpent in kernel is side-channel safe, so AES with AES-NI hw enabled
support could be practically better solution.
Anyway, I am just responding to the technical question, not the security one.
Serpent can be used with LUKS easily without problem.
Milan
prev parent reply other threads:[~2023-08-29 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 23:37 How to use Serpent Fabian Stargalla
2023-08-29 7:01 ` Milan Broz [this message]
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=159b42fe-d616-4a4f-8fbe-cff5067a57f5@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
--cc=fabestah@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