From owner-freebsd-bugs@freebsd.org Mon Sep 23 07:10:24 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 28F11E90EE for ; Mon, 23 Sep 2019 07:10:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46cFp80K9xz4df9 for ; Mon, 23 Sep 2019 07:10:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 0AC75E90EC; Mon, 23 Sep 2019 07:10:24 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0A8D2E90EB for ; Mon, 23 Sep 2019 07:10:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46cFp76VRzz4df8 for ; Mon, 23 Sep 2019 07:10:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A8743B2CF for ; Mon, 23 Sep 2019 07:10:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x8N7ANG2075620 for ; Mon, 23 Sep 2019 07:10:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8N7ANpq075619 for bugs@FreeBSD.org; Mon, 23 Sep 2019 07:10:23 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 240760] Caps lock key became a character in GELI passphrase entry after upgrading to 12.0 w/root-on-ZFS Date: Mon, 23 Sep 2019 07:10:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: arielmt@thornton2.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2019 07:10:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240760 Bug ID: 240760 Summary: Caps lock key became a character in GELI passphrase entry after upgrading to 12.0 w/root-on-ZFS Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: arielmt@thornton2.com A couple years ago, I installed 10.2-RELEASE amd64 on an Acer Aspire One Z (model ZC-700g, Intel Celeron J3160 CPU, 4GB RAM). During installation, I followed the instructions in the FreeBSD Handbook: In section 2.6, I chose Automatic Root-on-ZFS and changed the "Encrypt Disks?" option to yes, and followed the instructions in section 2.6.4. Since then, I updated and upgr= aded following the handbook, release notes, and errata documents. Yesterday, I upgraded from 11.2-RELEASE to 12.0-RELEASE. After shutting do= wn to boot into the new kernel, I entered my passphrase at the GELI prompt whi= ch appears before the boot menu. However, the boot process stalled after the kernel booted, as if I entered a bad passphrase. Double-checking and slowi= ng down my typing had no effect: I was entering the correct passphrase, consistent with all previous startups, but it wasn't being recognized. My current passphrase consists of runs where the letters are uppercase, long enough that it's easier to type with caps lock on. While trying to figure = out what I was doing wrong, I noticed the GELI keypress spinner advance a step = when I turned caps lock on and again when I turned it off; this is new. My passphrase wasn't recognized until I typed it in without the benefit of caps lock. Steps to reproduce: Install (or upgrade to) FreeBSD 11.2-RELEASE amd64 with "Automatic Root-on-ZFS," change "Encrypt Disks?" from NO to YES, set a passphrase including uppercase letters. Then, upgrade to 12.0-RELEASE. Expected behavior: The passphrase typed at the boot-time GELI prompt is recognized whether capitals are typed with Shift pressed or capitals are ty= ped with caps lock on. Actual behavior: The passphrase is recognized if capitals are typed with Sh= ift pressed, but it is not recognized if the caps lock key is used during passphrase entry. --=20 You are receiving this mail because: You are the assignee for the bug.=