Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Apr 2022 05:40:44 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 263233] bsdinstall: 'ZFS Configuration' has become a confusing heading for encryption-related stages of installation of FreeBSD
Message-ID:  <bug-263233-227@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 263233
           Summary: bsdinstall: 'ZFS Configuration' has become a confusing
                    heading for encryption-related stages of installation
                    of FreeBSD
           Product: Base System
           Version: CURRENT
          Hardware: Any
               URL: https://github.com/freebsd/freebsd-src/tree/main/usr.s
                    bin/bsdinstall
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: grahamperrin@gmail.com

>From <https://www.tumfatig.net/images/2017/Vultr-FreeBSD-ZFS-root-17.png>; in
2017:=20

> ZFS Configuration
>=20
> Enter a strong passphrase, =E2=80=A6

The same wording is used in the current installer for FreeBSD.=20

Anyone who knows of OpenZFS support for encryption might, naturally, assume
that it's a passphrase for OpenZFS encryption.=20

Not so.=20

Similarly, from
<https://www.tumfatig.net/images/2017/Vultr-FreeBSD-ZFS-root-19.png>:=20

> ZFS Configuration
>=20
> Initializing encryption on selected disks, =E2=80=A6

There's less potential for confusion, because OpenZFS encryption does not a=
pply
at the disk level, but only slightly less (because not all people will make=
 the
distinction).=20

Generally:=20

* need to review the appropriateness of 'ZFS Configuration' as a heading.

--=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-263233-227>