![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
You need a phone, tablet, or other device that’s been rooted.
Damit
You need a phone, tablet, or other device that’s been rooted.
Damit
It doesn’t though? IANAL but as far as I can tell you can fork, modify and redistribute it as long as you provide the source code to your users.
It’s AGPL-3.0 so… https://www.tldrlegal.com/license/gnu-affero-general-public-license-v3-agpl-3-0
For now
That’s not Firefox forcing you to update, you had Firefox open while you (/your package manager) was updating Firefox and after the update was done Firefox needs to be reopened. To prevent this you just have to …not update Firefox while it is running.
Not yet ready for daily use!
We were on the verge of greatness, we were this close.
But those only have a short life, they don’t get many updates iirc.
your staff play document format police.
Often the email filter will just convert everything not allowed to PDF.
Last time I enabled secure boot it was with a unified kernel image, there was nothing on the EFI partition that was unsigned.
Idk about the default shim setup but using dracut with uki, rolled keys and luks it’d be secure.
After this you’re protected from offline attacks only though, unless you sign the UKI on a different device any program with root could still sign the modified images itself but no one could do an Evil Maid Attack or similar.
Well, it rules out an evil maid attack and maybe jumping over a dual boot setup.
replace a file on the EFI partition.
Doesn’t this mean that secure boot would save your ass? If you verify that the boot files are signed (secure boot) then you can’t boot these modified files or am I missing something?
Would this even cause a kernel panic? I think this just causes a userland “panic”