[Bug 254966] geli setkey not working with detached provider
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat May 8 20:49:15 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254966
Michael Büker <freebsd at michael-bueker.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |freebsd at michael-bueker.de
--- Comment #2 from Michael Büker <freebsd at michael-bueker.de> ---
I can confirm this bug. It exists in 12.2-RELEASE-p6 and 13.0-RELEASE, but
_not_ in 11.4-RELEASE-p9.
Steps to reproduce:
# mdconfig -a -t malloc -s 10M -u md10
# echo aaa | geli init -J - md10
# echo aaa | geli attach -j - md10
# geli status md10.eli
# geli detach md10
At this point, md10 is a geli volume with passphrase "aaa". Now, observe the
failure of geli setkey:
# geli setkey -n0 md10
This command asks for the existing passphrase and then does nothing. It
_should_ ask for the new passphrase (and correctly does so on 11.4-RELEASE).
The same happens when using passfiles:
# echo aaa > oldkey
# echo bbb > newkey
# geli setkey -n0 -j oldkey -J newkey md10
At this point, "aaa" is still the passphrase in slot 1 of md10.eli, even though
it should be "bbb". Confirm this by:
# geli attach -j newkey md10
... which fails, and:
# geli attach -j oldkey md10
... which succeeds (but shouldn't).
Note that all is well when using geli setkey on md10.eli when it is attached.
This bug only affect unattached volumes.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-geom
mailing list