this post was submitted on 26 Aug 2025
44 points (97.8% liked)

Linux

59502 readers
430 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
44
Debian, encrypted boot, how to increase password attempts? (slrpnk.net)
submitted 2 months ago* (last edited 2 months ago) by boredsquirrel@slrpnk.net to c/linux@lemmy.ml
13 comments fedilink hide all child comments
 

Since Debian 13 (Trixie), when using the default FDE which uses grub to decrypt the luks partition, I have a single attempt

When the password is mistyped there is a long pause (over 10 seconds) and then the error appears.

I already tried increasing the max tries, which seems to be set to 1 when a keyfile is used.

The config/script seems to be in /usr/share/initramfs-tools/scripts/local-top/cryptroot.

I copied that to /etc/initramfs-tools/scripts/local-top/cryptroot and replaced the value CRYPTTAB_OPTION_tries=1 with 10 using find/replace (ansible stuff).

I think this has no effect though and doing so (might be a different issue) breaks boot entirely 💀

More info:

  • by default when legacy boot (BIOS) is available, Debian will install grub to the MBR. This is where it happens
  • when forcing or prioritizing legacy boot and using GPT, debian somehow boots from a 300MB efi partition, the same happens though, one attempt
you are viewing a single comment's thread
view the rest of the comments
[–] ferric_carcinization@lemmy.ml 3 points 2 months ago* (last edited 2 months ago) (1 children)

As it's a bootloader, it should make almost no difference which distribution was used to install it. (I'm not sure if Debian patches their GRUB.) I just used Arch as an example, as it is famous for being up to date. And, no matter where it's installed from, if you've made changes to GRUB's configuration, you'll have to copy it over to the live distribution to keep your changes.

Yes, Debian Sid might be more familiar for Debian users, but that's it.

Edit: You said "get the grub debs from Debian sid", but installing Sid packages on non-Sid systems isn't something that you should do.

[–] communism@lemmy.ml 0 points 2 months ago (1 children)

Why install it from a package manager at that point? It's probably more of a pain to get an Arch package working on Debian than it is to just build GRUB from source and install it according to whatever instructions GRUB distributes

[–] ferric_carcinization@lemmy.ml 3 points 2 months ago

I meant the following:

  1. Find out the Debian package is too old
  2. Create Arch Live USB
  3. Boot Arch Live USB
  4. Copy GRUB config from the Debian install to the current Arch live system
  5. Install the up-to-date GRUB while in the Arch environment

The bootloader installer package is distro dependent, the bootloader the package installs isn't. You can boot Debian no matter if the GRUB is installed from Debian stable, Debian Sid, Arch, Fedora or even FreeBSD. Otherwise, dual booting wouldn't work.

Like I said, I've done that before, though with SystemD Boot instead of GRUB, which was a bit simpler due to how the bootloader is configured.