Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Mar 2016 11:16:30 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 208251] [regression] Bogus geli passphrase prompts after r296963
Message-ID:  <bug-208251-8-allgNwdzXm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208251-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-208251-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208251

Fabian Keil <fk@fabiankeil.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|Closed                      |Open

--- Comment #6 from Fabian Keil <fk@fabiankeil.de> ---
Reopen as the patch only solves the problem for GELI boot
partitions without passphrase.

>From the commit message (which bugzilla seems to hide really well):

"r296963 added support for GELI boot devices with passphrases
and without keyfiles but the passphrase prompt was shown for
all boot devices, including those that only required a keyfile,
or that required both a keyfile and a passphrase.

Attaching such devices (obviously) did not work and as a result
r296963 broke unattended booting from these configurations.

This commit suppresses the promt for passphrase-less boot
devices but does not suppress it for boot devices that require
both a passphrase and a keyfile as this currently can't be
deduced from the GELI metadata.

Probably a new GELI on-disk flag should be added to solve this."
https://bz-attachments.freebsd.org/attachment.cgi?id=3D168646

The problem that geli-encrypted partitions on slices aren't
detected properly has not been solved either.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208251-8-allgNwdzXm>