Although passwords can be encrypted, they can be edited and modified. What command can be used to prohibit this function?
China DOS Union
Union site: www.cn-dos.net Forum site: www.cn-dos.net/forum
DOS stands for freedom, openness and progress. Let us work hard, learn from the openness and GNU spirit of FreeDOS and Linux, and together build and grow a free GNU GPL world!
中国DOS联盟论坛 » GRUB4DOS、SYSLINUX及其它启动管理软件讨论专区 » GRUB4DOS version 0.44, can you disable the edit command at the boot screen?
View 1,597 Replies 3
Original Poster
Posted 2008-08-09 23:18 · 中国 香港 电讯盈科有限公司
Floor 2
Posted 2008-08-10 09:53 · 中国 河南 南阳 电信
银牌会员
★★★★
不甘寂寞的人
Credits 2,491
Posts 1,115
Joined 2003-09-24 00:00
22-year member
UID 10292
Gender Male
Posts 1,115
Joined 2003-09-24 00:00
22-year member
UID 10292
Gender Male
Status Offline
The `password` command needs to be used together with the `lock` command.
When the `lock` command is executed, it displays a password input interface, requiring the user to provide a password. If the user fails to provide the correct password, the execution result of the `lock` command is an error, and then subsequent commands cannot be executed.
You can place the `password` command before `title`, so that the entire menu will be protected. Unless you enter `p` as prompted on the screen and provide the correct password (which is equivalent to unlocking), all menu items cannot be changed. But at this time, the user can execute all the menu items in your existing menu. Unless you use `lock` to lock a certain menu, the user will not be able to execute the commands in the corresponding menu.
Note that it is more appropriate to place `lock` in the first statement after `title`, because only when the program executes to `lock` will it prevent the user from further execution. You lock all the menu items that need to be protected, that is, after each `title` line, a `lock` is needed, otherwise, the menu item is not protected and the user can execute it.
Please refer to the official manual of GNU GRUB legacy. What I said may not be accurate. Please refer to the official manual of GNU GRUB legacy.
[ Last edited by 不点 on 2008-8-10 at 10:00 AM ]
When the `lock` command is executed, it displays a password input interface, requiring the user to provide a password. If the user fails to provide the correct password, the execution result of the `lock` command is an error, and then subsequent commands cannot be executed.
You can place the `password` command before `title`, so that the entire menu will be protected. Unless you enter `p` as prompted on the screen and provide the correct password (which is equivalent to unlocking), all menu items cannot be changed. But at this time, the user can execute all the menu items in your existing menu. Unless you use `lock` to lock a certain menu, the user will not be able to execute the commands in the corresponding menu.
Note that it is more appropriate to place `lock` in the first statement after `title`, because only when the program executes to `lock` will it prevent the user from further execution. You lock all the menu items that need to be protected, that is, after each `title` line, a `lock` is needed, otherwise, the menu item is not protected and the user can execute it.
Please refer to the official manual of GNU GRUB legacy. What I said may not be accurate. Please refer to the official manual of GNU GRUB legacy.
[ Last edited by 不点 on 2008-8-10 at 10:00 AM ]
因为我们亲手创建，这个世界更加美丽。
Floor 3
Posted 2008-08-10 10:43 · 中国 香港 电讯盈科有限公司
Thank you, the second-floor owner. I will try the settings you mentioned later.
Floor 4
Posted 2008-08-10 15:29 · 中国 四川 德阳 电信
Originally posted by kelvinso at 2008-8-10 10:43 AM:
Thanks to the second-floor landlord
Hehe, the second-floor landlord.
The brother above still doesn't know that this second-floor landlord is currently the main author of grub4dos
Forum Jump: