Your message dated Thu, 1 Jun 2023 21:04:58 +0200
with message-id <20230601190458.tgnsgfo3uty26...@mraw.org>
and subject line Re: Bug#694154: debian-installer: Preseeding isn't possible
for partman-crypto (encrypted LVM)
has caused the Debian Bug report #694154,
regarding debian-installer: Preseeding isn't possible for partman-crypto
(encrypted LVM)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
694154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20121114
Severity: normal
Tags: d-i
Hi,
if my understanding of partman-crypto's blockdev-keygen's code is
correct, one isn't able to preseed the passphrase for encrypted LVM:
http://anonscm.debian.org/gitweb/?p=d-i/partman-crypto.git;a=blob;f=blockdev-keygen
(See get_passphrase; also, my experiments seem to agree.)
The comments at the top even say:
# This handles sensitive data that must not be swapped out
# or written out to disk unencrypted.
#
# Important: before running this script the caller has
# to check for unsafe swap partitions. This is done in
# choose_method/encrypt/do_options.
#
# Assumption: This runs as part of d-i. Therefore, temp
# files outside of /target reside in a ramdisk. Process
# information (think [ "$pass" ]) is not exposed to anyone
# but the installing user.
If we are to continue disallowing preseeding those parts, I believe
it would be nice to have that documented in the example preseed file.
Comments anyone?
Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Hi,
Some notes on the general bug mail/management:
James Addison <j...@jp-hosting.net> (2023-06-01):
> Source: partman-crypto
> Followup-For: Bug #694154
> Control: fixed -1 partman-crypto/77
Can't you use `bts -m show $N` instead of using followup-for? It's
always a mess when it comes to tracking other recipients… Also, you
could use reply-all, and not miss the submitter (like in this case).
> It looks like this was resolved[1] in partman-crypto version 77
> (Debian bug #656710 / Ubuntu launchpad issue #546405 for the same) -
> can we close this bugreport?
>
> [1] -
> https://salsa.debian.org/installer-team/partman-crypto/-/commit/be0a3afab31ba7a174047289c3aa5df179c6a794
Either we can or we cannot; adding fixed without closing only goes
half-way and feels weird and inconsistent…
In this specific case: closing.
Cheers,
--
Cyril Brulebois (k...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
--- End Message ---
