From: Milan Broz <gmazyland@gmail.com>
To: Matthias Schwartz <m.schwartz@hs-mannheim.de>, dm-crypt@saout.de
Subject: [dm-crypt] Re: 32/64-bit compatibility: Plain encryption of USB device partition
Date: Wed, 24 Mar 2021 22:56:33 +0100 [thread overview]
Message-ID: <585a5280-daee-0ecd-c820-0e372904d221@gmail.com> (raw)
In-Reply-To: <c8173305-fbef-f200-5210-efb0b233c3a4@hs-mannheim.de>
On 24/03/2021 11:42, Matthias Schwartz wrote:
> Hello,
>
> I didn't found compatiblity information in the FAQ:
>
> Questions:
> - 32-bit system and 64-bit systems compatible?
> - little endian and big endian systems compatible?
>
> I like to do a plain encryption of a SD-Card partition but it seems that
> an encryption created on a 64 bit system can't be mounted on a 32 bit
> system.
>
> Should this work?
Everything should work, it is platform independent.
The only exception would be 32bit system compiled without 64bit sectors compatibility,
there a device size is limited (but that is not limitation of dmcrypt but
the whole system, it applies to fs etc).
But better please use LUKS for key management.
m.
> On 64 bit system:
> cryptsetup --cipher=aes-cbs-essiv:sha256 --hash riepmd160 open
> --type=plain /dev/sdb1 key
> mkfs /dev/mapper/key
>
> On 32 bit system
> cryptsetup --cipher=aes-cbs-essiv:sha256 --hash riepmd160 open
> --type=plain /dev/sdb1 key
> mount /dev/mapper/key /mnt
>
>
> Best Matthias
>
>
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
prev parent reply other threads:[~2021-03-24 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 10:42 [dm-crypt] 32/64-bit compatibility: Plain encryption of USB device partition Matthias Schwartz
2021-03-24 21:56 ` 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=585a5280-daee-0ecd-c820-0e372904d221@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=m.schwartz@hs-mannheim.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;
as well as URLs for NNTP newsgroup(s).