First of all, thank you.

As you see, I use a rolling-release distro, so I was courious if there was a config file to edit, to put the "--unrestricted" option to my menuentries automatically, as I regenerate my grub.conf file. ( That happens often. ) But nobody explained it.

I will try to figure it out myself.

And I've read the manual. But as the BEHAVIOUR has changed, I did not understood fully, what happened there. ( I'm not the only one, just look around on the web. )

And one last thing. Forums are there to help and to guide.
So, it is RTM, not RTFM. This is what discourages people to ask.

Thank you.

Software version is: grub-common-2.0.0-1
                     grub-bios-2.0.0-1

Find the original bug post at the arch linux forums.

( https://bbs.archlinux.org/viewtopic.php?id=144572 )

I've newly installed arch on a laptop, and ( paranoid as always  ) I wanted to password-protect the menu editing in grub2, as described in the wiki. It always worked until now, but now the entries became password-protected even against booting. (That actually works, when I type in user/password)

What I did was :

generate a hashed pass with

# grub-mkpasswd-pbkdf2

and I've put the following code at the end of /etc/grub.d/00_header:

--------------------------------

cat << EOF

set superusers="myname"
password_pbkdf2 myname grub.pbkdf2.sha512.10000.looooooooooooooongstring

EOF

-------------------------------

I've seen that there was a package update of grub2-common and grub2-bios the 28 june, maybe something has changed upstream?

How can I now setup grub2 to be password-protected only against EDITING and not BOOTING?

[EDIT: I can regenerate the same behaviour on a system running in Virtualbox too.]