In my case it was soundcore's app (no, openscq30 didn't work), so it had a need for network access to update the firmware, for example, I just didn't want to give it at the moment. As for being poorly made, also not exactly: as I've mentioned, android gives this permission by default, and it's reasonable to assume it stays so. Graphene basically "breaks userspace" here.
I remember some particular apps not liking that one. Basically it exposes the permission that's otherwise always granted, and if the developers didn't make a catch all for network errors, the app crashes. Mobile data usage → allow network access favors better in that regard.
As always, the answer is "depends". It shouldn't hurt unless you're dual-booting windows (they used it last year as a weapon in their "mess up grub" game), but, Imo, it's worth the trouble if:
So, a lot of ifs, and a necessity to store the uefi password somewhere safe, as those may be a pita to reset.
As for standalone stuff -- idk, it might protect you from malware injecting itself into the bootloader or something, but given there's likely no chain of trust (I.e. the bootloader doesn't check what it bootloads), it can move in on some later step.
This, but backtrack 5 (the one just before kali). On a laptop that'd take several eternities to brutforce an md5 🤣
Reminded me one of the vids of f4mi, although that ladiy's approach is far more beautiful. Basically, she took advantage of ai scrapers relying on subtitles and YouTube allowing for pretty advanced styling of those very subtitles to insert garbage that only bots will see.
To those interested in the details, https://www.youtube.com/watch?v=NEDFUjqA1s8 (selecting a working invidious instance is left as an exercise for the reader)
Quite simple, actually. If you want to do a thing that violates a law, you modify the law to allow the thing.
Well, technically anywhere from 5 to 40, but I still have a nice chance to grow old before libreboot starts building. Also, still slower than dial-up.
All clothes are no-iron clothes if you DGAF enough :)
Decided to share an older "project" of mine - ms sculpt wireless to wired conversion (also, it runs qmk, so we get all its features). A sensible person would order a custom pcb (such projects exist on the web, take a look if you're interested), but I went with removing all the components except from the ribbon cable connector, sending the PCB smooth, gluing a piece of discount card to isolate the traces, gluing a Chinese rp2040 on top, and wiring all the necessary traces to it. No, it wasn't fun. Yes, it works.
Bonus: when I disassembled it now I found out the type-c wasn't soldered well and decided to separate from the board:
So, here we go: using phone as a poor man's microscope (note: also, still works)
The end result kinda doesn't give it out, so whatever (insert your frontend -- backend jokes here)
Incorrect: the backdoored version was originally discovered by a Debian sid user on their system, and it presumably worked. On arch it's questionable since they don't link sshd with liblzma (although some say some kind of a cross-contamination may be possible via a patch used to support some systemd thingy, and systemd uses liblzma). Also, probably the rolling opensuse, and mb Ubuntu. Also nixos-unstalbe, but it doesn't pass the argv[0] requirements and also doesn't link liblzma. Also, fedora.
This is good, but I prefer this 
Should've installed linux 🤷
Yeah, those mailing lists used to have some quite funny stuff; my favorite so far is smth along the lines of "whoever thought this was a good idea should be retroactively aborted".
But, on the other hand, damn it's toxic. Should've really sucked to work on the kernel back then.
It's feRd