dm-crypt.saout.de archive mirror
 help / color / mirror / Atom feed
* [dm-crypt] SSD encryption using cryptsetup
@ 2020-10-10  3:06 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
  0 siblings, 2 replies; 4+ messages in thread
From: KRISHNAJA MENON @ 2020-10-10  3:06 UTC (permalink / raw)
  To: dm-crypt

[-- Attachment #1: Type: text/plain, Size: 482 bytes --]

Hi,

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
2. luksOpen, create partition and luksClose on x86 machine
3. luksOpen (decrypting/unlocking) on the SSD on an aarch64 machine using
the same password fed in step 1 fails

Also tried step 1 and 2 on aarch64 and 3 on x86 - fails
Does the cipher algorithm used while formatting depend on the architecture?

Thanks,
Krishna

[-- Attachment #2: Type: text/html, Size: 1239 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] Opening container created on aarch64 fails on x86_64 and the other way around; was: SSD encryption using cryptsetup
  2020-10-10  3:06 [dm-crypt] SSD encryption using cryptsetup KRISHNAJA MENON
@ 2020-10-10  6:54 ` Michael Kjörling
  2020-10-10 17:48 ` [dm-crypt] " Milan Broz
  1 sibling, 0 replies; 4+ messages in thread
From: Michael Kjörling @ 2020-10-10  6:54 UTC (permalink / raw)
  To: dm-crypt

On 9 Oct 2020 20:06 -0700, from krishnajamenon92@gmail.com (KRISHNAJA MENON):
> Also tried step 1 and 2 on aarch64 and 3 on x86 - fails

"Fails" in what manner? Please show the exact output, preferably from
running cryptsetup with --debug. Also please specify the exact version
of both cryptsetup and the kernel that you're running on each system.
uname -a might be a good start.

-- 
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
 “Remember when, on the Internet, nobody cared that you were a dog?”

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] SSD encryption using cryptsetup
  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 ` Milan Broz
  2020-10-10 17:56   ` KRISHNAJA MENON
  1 sibling, 1 reply; 4+ messages in thread
From: Milan Broz @ 2020-10-10 17:48 UTC (permalink / raw)
  To: KRISHNAJA MENON, dm-crypt

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] SSD encryption using cryptsetup
  2020-10-10 17:48 ` [dm-crypt] " Milan Broz
@ 2020-10-10 17:56   ` KRISHNAJA MENON
  0 siblings, 0 replies; 4+ messages in thread
From: KRISHNAJA MENON @ 2020-10-10 17:56 UTC (permalink / raw)
  To: Milan Broz; +Cc: dm-crypt

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-10-10 17:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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 NNTP newsgroup(s).