Good question. But if someone unauthorized has physical access to your system, you already have worse problems to worry about..
this post was submitted on 26 Apr 2026
42 points (92.0% liked)
No Stupid Questions
47927 readers
730 users here now
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here. This includes using AI responses and summaries.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
founded 2 years ago
MODERATORS
Yeah, I've never even thought about using PW BIOS protection since someone could always just pop out the drive and do whatever with it. I guess if it's a soldered drive it makes slightly more sense but still easily overcome by anyone who's determined enough
Full disk encryption is what you want really
It’s apparently not at all a priority for the devs. They don’t seem to care if your laptop is stolen and the drive is wiped.
Data exfiltration was their only concern and drive encryption solves that.
What am I missing? If someone steals your laptop they can just mountb the drive in their own hardware irrelevant of your bios.
Not if it's encrypted.
When the drive in encrypted, you need a (very very long) encryption key to read it. Otherwise, the data is obfuscated and can't be read by bad actors. This encryption key is essentially impossible for (non-quantum) computers to crack as it would take too long
Ironically it's also the best way to make sure your data isn't leaked when selling drives second hand.
Full encrypt it, roll the key, and now you have a drive with no readable content for sale.
When the next person come along they will likely ignore the password and do their own thing.
Wouldn't something like DBAN do the same thing but with less operations on the drive?
For spinning rust drives, yes. But for SSD no. Because of how the SSD store data it isn't guaranteed to be overwritten.
That's definitely true. In that case encrypting the SSD makes more sense yeah (or any flash storage)
Even quantum computers will not be able to break AES fast enough
They don’t seem to care if your laptop is stolen and the drive is wiped.
Even if they did care, what could they do about it? The thief could remove the drive and wipe it with their own computer, or even just physically destroy the thing. The only point of a BIOS password is to make the laptop a pain for a thief to resell.
I can pull and wipe the drive in any laptop in 1-10min. Even in high end corporate almost no one sets a BIOS password, the few that do are doing it more to keep users out of those settings than as security. And even if you set it the on a lenovo, dell, hp, etc... There's usually a manufactur password or pins you can short to reset it.
Maybe from another perspective, BIOS passwords are a weak defense. The BIOS settings storage are powered by a small battery and can be reset by removing the battery. As others have mentioned, protecting the data is the priority and done through encryption. Protecting the device itself is not really possible in most cases anyways.
Coreboot isn't the same thing as the BIOS. It's the motherboard chipset firmware and all it does is initialize the hardware, which is only part of what BIOS/UEFI do.
Check out something like Heads.
Anyway, wiping your drive is the least of your worries when it comes to software attacks. You should be keeping regular backups of your data anyway. You want to prevent malicious actors from accessing your data, which, if they have physical access to your hardware, increases the risk a great deal. Heads will help prevent against evil maid attacks, although the bad actor can still reflash the BIOS chip physically. Full disk encryption (assuming your computer is off at the time that your computer gets stolen/hijacked) is the goto method of securing the data on your SSD.
sigh To actually answer your question:
Coreboot itself is just init firmware that contains a payload, such as Seabios, GRUB or Tianocore.
Those can have passwords (or also not, Seabios can't, as far as I'm aware).
There's a Libreboot site on how to lock down GRUB.
Basically, you have to flash your own config by adding your password hash and replacing the one in the ROM with e.g. cbfstool. It may sound scarier than it is.
Besides having less features than many proprietary BIOSes, I prefer the flexibility of having your own config to play around with. You can also create custom entries to boot fully encrypted RAIDs and such stuff.
(I sighed because many answers were about BIOS passwords not being effective anyway, which, to me, is dog shit, because of course you do not want somebody random to be able to just boot a USB from your device and screw up your system. And no, it does not reset itself when you take out the CMOS battery.)
The Lenovo security is only as good as their design and testing which is probably dogshit anyway.
BIOS password is theatre
In the best possible scenario, a BIOS/UEFI password lock will prevent an adversary from using the computer as-is. If the adversary has an objective to quickly fence the computer, then this objective is foiled. Note that preventing the computer from physical access would also foil this objective, since that prevents the adversary from even accessing the machine.
But that's the best case. In a more-worse case scenario, the adversary wants to steal data from the computer. A firmware password will be useless if the adversary removes the HDD or SSD from the machine. This is, instead, correctly solved with drive-level encryption, using a password or smart card to unlock.
The reason why open-source firmwares (BIOS/UEFI) might be uninterested in implementing a password is because: 1) preventing physical access is more effective, and 2) because it's arguably a form of security theatre: commercial firmware vendors include a password feature because some customer once asked for it, but not with security as a well-thought objective. Open-source projects have a habit of not implementing pointless features.
TL;DR: physical access to a machine is fatal to any and all security protections
Those alternative bootloaders are there to get around the intel management engine, a potential backdoor (AMD has PSP, same deal). At least, that's their most prominent advantage IMO.