Date: Mon, 25 Jan 2016 11:38:28 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 206600] geli with new "setkey -n 1" pwd is rejecting pwd 3 times, than ascing for gpt/zfs0.eli pwd Message-ID: <bug-206600-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206600 Bug ID: 206600 Summary: geli with new "setkey -n 1" pwd is rejecting pwd 3 times, than ascing for gpt/zfs0.eli pwd Product: Base System Version: 10.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: marc.arnold.bach@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Hello, I have a test installation in a vmware and zpool status shows a root-pool in /dev/da0p4.eli => encrypted blockdevice Its result of bsd's "auto zfs root" installation with encryption flag set to "yes" Symptom: System reboots and is rejecting the new pwd (which very short and simple and very independent from keyboardlayout => asdfg) It asks first generically for geli pwd... later 3 times explicitly for /dev/da0pa while counting down "free tries". At the end it asks for /gpz/zfs0.eli pwd and is booting with asdfg string as pwd After reboot zpool status shows the rootpool to be located at gpt/zfs0.eli not dev/da0p4 anymore Steps to reproduce this: - Adding a new password in slot 1 is succesfull with root# geli setkey -n 1 /dev/da0p4 [...blabla] may exist old metadata in /var/backups [...blabla] root# reboot Some tests I made: - Using initial pwd from init "qwert" works still fine and I can start system with one keyboard action qwert-Enter - Using setkey -n 0 will overwrite first key succesfully but will end up in rejecting pwd 4 times later again. - By the way I opened another ticket because restoring the metadata to a working pwd is "not permitted" as well. Regards Marc -- 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-206600-8>