The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
August Levasseur said:
don’t realize they’re not actually asking you to give anyone your ID.
Click to expand...
I think you're retarded.
August Levasseur said:
this shit is not the end of the world
Click to expand...
No, it's not. 8 billion people won't die if this happens. They also won't die if we all collectively agree that it's fine to kill you specifically for no reason at all, but it would set a bad precedent.
 
gpg said:
Ubuntu is removing a huge number of supported file systems from their shipping version of the GRUB boot loader.

LVM, LUKS, btrfs, hfsplus, xfs, zfs, & mdraid.

They are also disabling images (like JPG) in GRUB.

Click to expand...
This is the reply that indicates what they're conspiring to do
Have you considered switching to systemd-boot instead? It’s the minimal bootloader you’re looking for, and it integrates into systemd-based systems well anyway.
Click to expand...
For 28.10: "We've already stripped out all the useful features from GRUB anyway, why not mandate systemd-boot?"
 
There's no excuse for removing Luks, LVM and mdraid. Those are excellent and widely used, and encryption is very important to anyone who cares about their privacy.
But stripping ZFS out of GRUB I agree with. It's a trap option, GRUB's support for it has always been extremely limited. It forces you to disable a large number of useful features, takes ages to import a pool, and even longer just to load the encryption key. If you want to boot ZFS from GRUB you will very much want to do so from a (signed!) kernel stored on the EFI partition rather than from a kernel stored on the ZFS pool.
 
The Ubuntu thread has already been locked down from knee jerk reactions. At first, I thought this janitor was actually a Canonical employee and was getting PAID, which is something truly unthinkable. I then checked and his badge is a round "Ubuntu member" and not the similar but different, rectangular "Canonical" badge so thankfully his salary is still $0.00 at the time of writing.
ub (2).png

>rust rewrite of GRUB
Everything must be RUST, Anything lower level than java is chud coded and scary.
ub (1).png

i440BX said:
I think they desperately try to implement remote attestation in Linux.
Click to expand...
What would Ubuntu be able to do if it implemented remote attestation and more importantly, what would the long term negative consequences be?
 
gpg said:
dumb question, but have you tried updating? im on arch and every time i had this issue i just had to sudo pacman -Sy, for apt i think its sudo apt update
Click to expand...
It wasn't the problem with updates on installed system, I couldn't even install it when using netinstall, it was either hanging on connecting to the mirror or throwing an error that installer couldn't connect.
I switched to live image, but the live installer is terrible. And I also realized that Devuan doesn't ship with dinit, as it was the init I wanted to try the most. So that's why I decided to go for Artix.
 
gpg said:
one thing i cant understand is why even remove images in grub? like what's the point?
Click to expand...
It's just an excuse to remove features so they can claim that systemd-boot isn't THAT much worse.

The pretext is that image parsers can be vulnerable to buffer overflows and if someone has a non-encrypted boot partition then some malicious actor could add a maliciously crafted image to exploit a (trusted, crypto signed) GRUB loader installed on the UEFI side of things to that boot partition. In theory that could allow an attacker to be able to run malicious code even if GRUB is set up to only load signed kernels.

This is some bullshit. I mean if someone is overwriting your grub.cfg to load malicious images you're probably fucked anyway. No doubt there is some relatively straightforward way that validation of GRUB background images based on say, the Ubuntu signing keys (to cover 99% of people who use a GRUB background image) or MOK keys (for the 1% remaining of anime perverts who want to put lolicon on their system boot screen) could be implemented. But... they don't care. They just want to make things worse, so they can later justify replacing their enshittified GRUB with pure shit (systemd-boot).
 
Locking boot options to UEFI only is retarded as it is mentally deficient niggerware with each board manufacturer managing to fuck it up in different manner. I never have had troubles with BIOS boot yet constant ones with this shit. The only reason why you would use it is for secure boot which in reality is nothing more than security theater. Not mentioning the fact that ironically UEFI is significantly more restrictive than BIOS when it comes to disk formatting(despite the usual claims) for example one can boot through BIOS without any disk table at all UEFI however wont boot without MBR or GPT
 
Hakase Shinonome said:
Can someone explain to me what secure boot even is? All I hear about it is “I need it to play Volarant” and “It sucks”. I want to know the actual technical definition.
Click to expand...
Basically a database (managed by Microsoft) of approved hashes for EFI executables. The idea was that Microsoft sign each Windows kernel with their private key, and the UEFI will check at boot if the kernel has a valid signature. If it doesn't, it refuses to boot. In theory it stops evil maid attacks, ie someone with physical access to the computer installing a rootkit. For the games, I guess the idea is that it would also stop kernel-level cracks from preempting the kernel-level anticheat (ie two malwares duking it out for dominance).
If you jump through some hoops you can Secure Boot sign your Linux kernel, but it's such a hassle (that needs to be redone each update) that almost everyone just uses a "shim", ie a tiny (signed) EFI executable that just automatically loads another (unsigned) EFI executable, making it no better than just turning Secure Boot off altogether.
 
I support Grub and it bothers me that Ubuntu is literally enshittifying Grub over non-issues. But on my rigs, Grub is a back-up bootloader, as the EFI boot ecosystem is developed to the point where you don't really need to think about bootloaders any more and can literally tell your "BIOS" (ie. your motherboard firmware) to boot your OS without requiring any additional stubs. You can even add your own CA to your "BIOS", sign your EFI bootloader yourself, and have attested, "secure" boot all the way into your OS... supposing your "BIOS" isn't locked down, which I hear isn't universally the case. Again, never hit that edge case myself. These days, if I want to run anything other than my daily driver Gentoo, I use my "BIOS" to choose. New kernel? I have a special "test" kernel I copy the new one over, boot from, and after a successful boot, copy it onto my "standard" kernel filename so it boots by default.

But I seem to be in the minority where I can make EFI boot faster and more reliably by manually configuring it than using shitty chinkware like Ventoy.

Even BIOS isn't that hard once you understand that the first 512 bytes of a drive run custom software, and then it's just a matter of eg. making sure that the first jump is within the 32-bit block-addressing limit, which is within the first 2TB (2**32 * 512).

Curry Teafag said:
Is there even any distro that doesn't use a shim for that?
Click to expand...
All about how you configure. I always start with Grub until I get the rough edges sorted out, as Grub is an EXCEPTIONALLY powerful debugging tool, which is another feature Noobuntu seems insistent on breaking.
 
Susanna said:
Basically a database (managed by Microsoft) of approved hashes for EFI executables. The idea was that Microsoft sign each Windows kernel with their private key, and the UEFI will check at boot if the kernel has a valid signature. If it doesn't, it refuses to boot. In theory it stops evil maid attacks, ie someone with physical access to the computer installing a rootkit. For the games, I guess the idea is that it would also stop kernel-level cracks from preempting the kernel-level anticheat (ie two malwares duking it out for dominance).
If you jump through some hoops you can Secure Boot sign your Linux kernel, but it's such a hassle (that needs to be redone each update) that almost everyone just uses a "shim", ie a tiny (signed) EFI executable that just automatically loads another (unsigned) EFI executable, making it no better than just turning Secure Boot off altogether.
Click to expand...
This is retarded.
 
You must log in or register to reply here.
Back
Top Bottom