From: Milan Broz <gmazyland@gmail.com>
To: Davide Marchi <danjde@msw.it>, dm-crypt@saout.de
Subject: Re: [dm-crypt] Encrypting DVD or CDROM from iso
Date: Wed, 18 Nov 2020 19:03:38 +0100 [thread overview]
Message-ID: <d4aa2671-94a5-311d-78ec-21bd3d760cd6@gmail.com> (raw)
In-Reply-To: <8064bad388c679e803ef903e92cc6ca5@msw.it>
On 18/11/2020 18:25, Davide Marchi wrote:
> Hi to All,
> finally I've found the right (and tested) procedure in this simple
> script, made by sowbug:
> https://gist.github.com/sowbug/c7f83140581fbe3e6a9b3ddf24891e77#gistcomment-3531970
The whole problem was that the size of device was wrongly calculated
from the debug:
> # Device size 16777216, offset 16777216.
This is apparently device size covering only LUKS2 header (default LUKS2 takes 16MB),
no data at all - then the error is expected.
> # All the code from
> http://billauer.co.il/blog/2010/10/encrypted-iso-dvd-luks-dm-crypt-fedora-linux/
>
> MB_COUNT=100
> VOL_NAME=MyVolName
> DIR_TO_COPY=/tmp/mydir
>
> # Make a 100MB disk image
> dd if=/dev/zero of=disk.img bs=1M count=$MB_COUNT
All you need to do here is just to allocate requested size for data + 16M for header.
(I have no idea why the original post tries to do is such complicated way.)
Also you do not need to physically write the file, sparse file creation is much
faster here (try sizes in GB), just run (dd can do this using seek=... option too)
truncate disk.img -s 100M
>
> # become root
> sudo su
>
> # write to the image
> # ****** NOTE that you'll be prompted three times for a passphrase
> losetup /dev/loop1 disk.img && \
This losetup step is not needed, loop is allocated automatically
if argument is a file (except for very old kernel where
automatic loop detach option is not yet available)
just run "cryptsetup luksFormat disk.img" and "cryptsetup open disk.img mybackupdisk"
> cryptsetup luksFormat /dev/loop1 && \
> cryptsetup luksOpen /dev/loop1 mybackupdisk && \
> genisoimage -R -J -joliet-long -graft-points -V $VOL_NAME -o
> /dev/mapper/mybackupdisk $DIR_TO_COPY
>
> # close the device
> cryptsetup luksClose /dev/mapper/mybackupdisk && \
> losetup -d /dev/loop1
This losetup is automatic on luksClose (so not needed) if you remove explicit loop allocation above.
Milan
next prev parent reply other threads:[~2020-11-18 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 17:25 [dm-crypt] Encrypting DVD or CDROM from iso Davide Marchi
2020-11-18 18:03 ` Milan Broz [this message]
[not found] <mailman.1.1605783602.13300.dm-crypt@saout.de>
2020-11-19 13:05 ` Davide Marchi
-- strict thread matches above, loose matches on Subject: below --
2020-11-18 14:59 Davide Marchi
2020-11-10 16:22 Davide Marchi
2020-11-10 16:59 ` Ondrej Kozina
2020-11-11 19:16 ` Carlos E. R.
2020-11-12 9:36 ` Milan Broz
2020-11-12 10:08 ` Carlos E. R.
2020-11-12 9:32 ` Milan Broz
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=d4aa2671-94a5-311d-78ec-21bd3d760cd6@gmail.com \
--to=gmazyland@gmail.com \
--cc=danjde@msw.it \
--cc=dm-crypt@saout.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