From: KRISHNAJA MENON <krishnajamenon92@gmail.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] SSD encryption using cryptsetup
Date: Sat, 10 Oct 2020 10:56:33 -0700 [thread overview]
Message-ID: <CAOnaoi9Scvwi3k_==jb=VYVd7pbODjSyv5VAN_mLoTGpN27Yqw@mail.gmail.com> (raw)
In-Reply-To: <1973481a-7b54-e7eb-ea29-f71bdb5acfe4@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Thank you for the clarification.
For some reason luksFormat was successful and I was able to encrypt the
disk using plain cbc. The format command passed without errors on both x86
and aarch64 without issues and I was able to feed a password. Also checked
isluKsdevice and luksDump, both were successful.
I will retry aes-cbc-essiv:sha256 and update. Will also share logs.
Thanks
On Sat, Oct 10, 2020, 10:48 AM Milan Broz <gmazyland@gmail.com> wrote:
> On 10/10/2020 05:06, KRISHNAJA MENON wrote:
> > Setup details:
> > Machine 1: Ubuntu x86_64
> > Machine 2: Linux-aarch64 (arm)
> >
> > 1. luksFormat an external SDD on x86 using *aes-cbc-plain:ripemd160* on
> x86 machine
>
> This cipher specification is nonsense, plain IV does not take arguments
> and it will
> be rejected by a recent kernels.
> (Moreover, CBC with plain IV mode is insecure due to predictable IV.)
>
> Please *do* *not* change defaults if you do not understand security impact.
> If you want CBC mode (XTS mode is default for LUKS), use
> aes-cbc-essiv:sha256
>
> (It should fail even in luksFormat, but you did not send neither debug
> output nor version related...)
>
> Milan
>
[-- Attachment #2: Type: text/html, Size: 1713 bytes --]
prev parent reply other threads:[~2020-10-10 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 3:06 [dm-crypt] SSD encryption using cryptsetup KRISHNAJA MENON
2020-10-10 6:54 ` [dm-crypt] Opening container created on aarch64 fails on x86_64 and the other way around; was: " Michael Kjörling
2020-10-10 17:48 ` [dm-crypt] " Milan Broz
2020-10-10 17:56 ` KRISHNAJA MENON [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='CAOnaoi9Scvwi3k_==jb=VYVd7pbODjSyv5VAN_mLoTGpN27Yqw@mail.gmail.com' \
--to=krishnajamenon92@gmail.com \
--cc=dm-crypt@saout.de \
--cc=gmazyland@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).