Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It was recommended to me by a colleague to set a grub password to further harden one of my systems. I don't think this is necessary as if you have physical access to the system you can just use a live cd to get into the system. Is there any reason to set a grub password that you may have come across?
You can set the BIOS to only boot from HDD, then put a password on the BIOS, then put a password on GRUB. This is helpful in a shared rack, where no one is likely to actually tamper with your box, because that would be obvious, but they might 'accidentally' plug their crash cart into your server,.. and if you don't have it properly locked down then you are hosed.
I actually think just setting a bios boot password is better than both ideas. You can still get around grub with bios locked to HDD (remove the HDD). However. If you set a bios boot password, your bios will refuse to boot anything unless it's provided with the password. There are bios settings for this. Set a user password and enable password on boot - done! I do this with all computers of mine (except standalone servers which restart on their own). Yes, the password is usually a max of 8 characters, but that is better still than just a grub password.
I actually think just setting a bios boot password is better than both ideas. You can still get around grub with bios locked to HDD (remove the HDD). However. If you set a bios boot password, your bios will refuse to boot anything unless it's provided with the password. There are bios settings for this. Set a user password and enable password on boot - done! I do this with all computers of mine (except standalone servers which restart on their own). Yes, the password is usually a max of 8 characters, but that is better still than just a grub password.
The CMOS password and Grub password is good enough for 'minor tampering' as i described above. If someone has full unimpeded access to your server then all bets are off.
Quote:
The system in question is a server. I wouldn't put a bios boot password on a server. Thanks for the info, though.
I agree with YankeePride13 there. I couldn't bring myself to have a password blocking a reboot, especially on a remote server.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.