https://bugs.kde.org/show_bug.cgi?id=433913

            Bug ID: 433913
           Summary: Please include an option to not encrypt /boot in order
                    to get the Plymouth decryption screen instead of the
                    Grub one
           Product: neon
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: Live/Install images
          Assignee: neon-b...@kde.org
          Reporter: 7d8ec5ed-2c18-46c5-9aec-31c49a4b2...@anonaddy.me
                CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 136344
  --> https://bugs.kde.org/attachment.cgi?id=136344&action=edit
grub decryption screen

SUMMARY
If you encrypt the entire system, you'll get a text-based, however, it has some
UX problems:

1. If you press enter (accidentally or not) while typing the password and start
typing again, GRUB will "leak" your password in the screen while entering GRUB
rescue. While decryption is in progress, keyboard should not register anything
aside from keyboard shortcuts.

2. Why just one incorrect attempt makes the GRUB enter in rescue mode? Three
attempts is a standard and it's better. Also, GRUB could show a keyboard
shortcut like "press R to enter rescue mode".

3. There is no message indicating that decrypting is in progress. You if don't
press enter correctly, you won't know if the decryption started or not.

4. Password characters doesn't appear in the screen as asterisks while you
typing. This is very useful to check if the system registered two characters
instead of one.

5. Backspace doesn't work. 

STEPS TO REPRODUCE
Encrypted the system when installing Neon.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21.1
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to