Bug 105368 - [geli] geli passphrase prompt malfunctioning when mounting encrypted fs at boot time
Summary: [geli] geli passphrase prompt malfunctioning when mounting encrypted fs at bo...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 6.2-BETA3
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-10 10:10 UTC by Jost Menke
Modified: 2018-01-03 05:13 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jost Menke 2006-11-10 10:10:21 UTC
When running FreeBSD 6.2-BETA3 or 6.1-RELEASE in a VMware session with encrypted root filesystem, the geli password prompt does not work when the root fs is mounted at boot time. I put kern.geom.eli.visible_passphrase=1 into /boot/loader.conf to see what's wrong, result: the keyboard doesn't work at all. When kbdmux is deactivated by putting hint.kbdmux.0.disabled="1" into /boot/device.hints, the behaviour changes: Keyboard partly works, but about 90% of all keystrokes are lost. The problem only seems to occur when mounting encrypted volumes at boot time. Other people on the mailing list report similar problems running FreeBSD on real hardware.

How-To-Repeat: - Install 6.2-BETA3 or 6.1-RELEASE with encrypted root fs in VMware player 
- Put kern.geom.eli.visible_passphrase=1 into /boot/loader.conf
- Also try to put hint.kbdmux.0.disabled="1" into /boot/device.hints
Comment 1 Aline de Freitas 2008-06-11 00:05:00 UTC
I'm running RELEASE-7.0, and with the same issues as this bug report.=20

=46rom my kernel config file:

# atkbdc0 controls both the keyboard and the PS/2 mouse
device          atkbdc          # AT keyboard controller
device          atkbd           # AT keyboard
options         ATKBD_DFLT_KEYMAP
makeoptions     ATKBD_DFLT_KEYMAP=3Dbr275.iso.acc
device          psm             # PS/2 mouse

#device         kbdmux          # keyboard multiplexer

In my loader.conf I've put kern.geom.eli.visible_passphrase=3D1, so I can s=
ee=20
what I type in prompt. Some keys from keyboard only work after pressing 2 o=
r=20
3 times.

=46reeBSD anderson-herzer.suite 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Mon Jun=
  9=20
21:21:00 UTC 2008    =20
aline@anderson-herzer.suite:/usr/obj/usr/src/sys/ANDERSON  i386

Thanks,
=2D-=20
Aline de Freitas - Chave p=FAblica: ID DE632016 / keys.indymedia.org
gpg --keyserver keys.indymedia.org --recv-keys DE632016
Comment 2 Arne Steinkamm 2009-10-05 03:22:47 UTC
I'm running RELEASE-7.2 and found the same problem of lost keystrokes.

It seems to be motherboard issue. After replacing a motherboard with the current
type this problem occurred.

It's a VIA C3-2 system with a VIA EPIA MII motherboard and a PS2 keyboard
connected with a console switch using the GENERIC kernel with loaded
geom_eli and geom_mirror modules.
Loading padlock makes no difference.

The crypted root filesystem is inside a geom mirror. The system boots from
a CF connected to an IDE port.

Adding kern.geom.eli.visible_passphrase is not a solution because this
makes the passphrase visible in the logs.

After falling through the passphrase questions you reach the failsafe
mountpoint dialog still inside the kernel. Here the keyboard works without any
problems.

Outside the kernel in userspace after boot there are also no problems with
the keyboard.

loader.conf:
padlock_load="YES"
geom_mirror_load="YES"
geom_eli_load="YES"
rootdev="mirror/stms1a.eli"
vfs.root.mountfrom="ufs:mirror/stms1a.eli"
kern.geom.eli.visible_passphrase=1

mirror/stms1a.eli was created with geli init -b.

Thanks.

.//. Arne
-- 
Arne Steinkamm         | Home:     Mail: arne<at>steinkamm<dot>com  IRC: Arne
Tel.: +49.89.299756    |    URL: http://WWW.Steinkamm.COM/  NIC-Handle: AS306
Laendstrasse 4         | 
80538 Muenchen GERMANY |
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:23 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped