You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for making this procedure available for Secure Boot. Following it to the letter works flawlessly in my InfinityBook Pro 14.
Still, there could be a minor issue for users who don't have US keyboards set-up in their Linux environment while setting up the one-time-password in the sudo mokutil --import TUXEDO_Computers_GmbH_Secure_Boot_Signing.crt call.
Explanation: When setting up the one-time-password, the terminal will work with your local keyboard layout which could be French, German, etc. and accept any special char that you throw at it. As long as the key and its repetition will normally agree, the special chars are set in there, ready to cause some head scratching upon the next reboot.
The MOK enrollment process (during this next reboot) happens in a US keyboard layout instead which will mess with you if you don't have a good mapping of where in the US layout your special chars go in the password...
The text was updated successfully, but these errors were encountered:
Thanks for making this procedure available for Secure Boot. Following it to the letter works flawlessly in my InfinityBook Pro 14.
Still, there could be a minor issue for users who don't have US keyboards set-up in their Linux environment while setting up the one-time-password in the
sudo mokutil --import TUXEDO_Computers_GmbH_Secure_Boot_Signing.crt
call.Explanation: When setting up the one-time-password, the terminal will work with your local keyboard layout which could be French, German, etc. and accept any special char that you throw at it. As long as the key and its repetition will normally agree, the special chars are set in there, ready to cause some head scratching upon the next reboot.
The MOK enrollment process (during this next reboot) happens in a US keyboard layout instead which will mess with you if you don't have a good mapping of where in the US layout your special chars go in the password...
The text was updated successfully, but these errors were encountered: