"The more complicated the plumbing, the easier it is to stop up the drain."
Thus the giant red flags with systemd.
At one point systemd mounted the ESP read-write, which meant an errant rm -rf / could brick your motherboard.
"The more complicated the plumbing, the easier it is to stop up the drain."
Thus the giant red flags with systemd.
At one point systemd mounted the ESP read-write, which meant an errant rm -rf / could brick your motherboard.
Here is why it’s unpatchable:
Despite Microsoft releasing new patched software, the vulnerable signed binaries have yet to be added to the UEFI revocation list that flags boot files that should no longer be trusted. Microsoft has not explained the reason, but it likely has to do with hundreds of vulnerable bootloaders that remain in use today. If those signed binaries are revoked, millions of devices will no longer work. As a result, fully updated devices remain vulnerable because attackers can simply replace patched software with the older, vulnerable software.
They should have thought of this when they created UEFI. Instead of being an extra security layer it is a source unpatchable vulnerabilities.
Maybe they did think about it being unpatchable for those reasons and were instructed to go ahead with it by an agency with enough brains and computer power to use it as a means of attacking for the "Great Hack Attack" false flag they are scheming up.maybe they'll tie it to a finacial collapse and blame the 'hackers' for no money available.
well fuck. I knew those newfangled UEFI bioses were no good
They don't exist for security. They exist for control.
malware that can hijack a computer’s boot process even when Secure Boot and other advanced protections are enabled
Burgers?
(post is archived)