Helvede

0 posts0 participants0 posts today

Kevin Karhan :verified:<a href="https://mastodon.social/@brouhaha" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@brouhaha</a> <a href="https://infosec.exchange/@catsalad" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@catsalad</a> yeah, <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> is really keen on forxing <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CensorBoot</a> down everyones throat despite publicly admitting that <a href="https://infosec.space/tags/TPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TPM</a> is insecure.<ul><li>Otherwise they would've used it in the <a href="https://infosec.space/tags/XboxOne" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XboxOne</a>!</li></ul>

Kevin Karhan :verified:<a href="https://social.heise.de/@heiseonline" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@heiseonline</a> tja, <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CensorBoot</a> in Aktion! <a href="https://infosec.space/tags/ToldYaSo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ToldYaSo</a>

Kevin Karhan :verified:<a href="https://infosec.space/@wravoc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@wravoc</a> IMHO, <a href="https://infosec.space/tags/TPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TPM</a> & <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UEFI</a> are both <a href="https://infosec.space/tags/Scams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scams</a> and neither can be trusted due to being <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backdoored</a> and <a href="https://infosec.space/tags/Bloatware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bloatware</a> respectably.Personally, I want a machine that is purposefully <a href="https://infosec.space/tags/incompatible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incompatible</a> with <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CensorBoot</a> by <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> (and thus <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows11</a>) by using <a href="https://infosec.space/tags/LinuxBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxBoot</a> / <a href="https://infosec.space/tags/NERF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NERF</a> and no TPM at all!Sadly I guess that means I've to use the <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RISCv</a> version of the <a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@frameworkcomputer</a> mainboard for that... The fact that UEFI has more code than the <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://infosec.space/tags/Kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kernel</a> with all it's drivers yet less than 100 contributors makes it inacceptable!

Kevin Karhan :verified:<a href="https://awscommunity.social/@Quinnypig" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Quinnypig</a> the sheer fact that <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> and <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows11</a> ain't banned across the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EU</a> to this day is an indictment to the <a href="https://infosec.space/tags/TechIlliteracy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechIlliteracy</a> of politicans in the <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@EUCommission</a> & <a href="https://respublicae.eu/@europarl_en" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@europarl_en</a> despite<ul><li><a href="https://infosec.space/tags/PRISM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PRISM</a></li><li><a href="https://infosec.space/tags/GoldenKeyBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GoldenKeyBoot</a> (aka. <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CensorBoot</a> got owned!)</li><li><a href="https://infosec.space/tags/CryptoAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CryptoAPI</a> <a href="https://infosec.space/tags/backdoors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backdoors</a> <a href="https://github.com/kkarhan/windows-ca-backdoor-fix" rel="nofollow noopener noreferrer" target="_blank">they refuse to acknowledge or fix at all</a>!</li><li><a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudAct</a></li><li>Unwillingness to comply with <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GDPR</a> out if the box</li></ul>and now<ul><li><a href="https://infosec.space/tags/Recall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Recall</a> aka. the worst disguised <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Govware</a> / <a href="https://infosec.space/tags/Spyware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Spyware</a> in existance that allows anyone to <a href="https://github.com/xaitax/TotalRecall" rel="nofollow noopener noreferrer" target="_blank">simply extract credentials</a> without the need to install a <a href="https://infosec.space/tags/Keylogger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keylogger</a>, <a href="https://infosec.space/tags/ScreenRecorder" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ScreenRecorder</a> and/or commit <a href="https://infosec.space/tags/ProvilegueEscalatiom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProvilegueEscalatiom</a> successfully at all...</li></ul>And since <a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@GossiTheDog</a> managed to get it running on a system w/o "<a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a>" acceleration aka. "<a href="https://infosec.space/tags/NPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NPU</a>" it's safe to assume that it'll be perfectly possible to retroactively shove it down everyones' throats without recourse!<ul><li>Actually there are options for recourse besides "<a href="https://infosec.space/tags/ThoughtsAndPrayers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ThoughtsAndPrayers</a>" that regulators like <a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bsi</a> would actually take this seriously: </li></ul>Like: Stop using <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a> and <a href="https://www.youtube.com/watch?v=PkKfV0ATrH4" rel="nofollow noopener noreferrer" target="_blank">get some help</a> migrating away from it to a good <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> distro!<a href="https://infosec.space/tags/WhatYouAllowIsWhatWillContinue" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatYouAllowIsWhatWillContinue</a>

Kevin Karhan :verified:<a href="https://peoplemaking.games/@eniko" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@eniko</a> if it was about <a href="https://mstdn.social/tags/ITsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITsec</a> it would've been implemented in a way that lets <a href="https://mstdn.social/tags/users" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#users</a>, not <a href="https://mstdn.social/tags/BigTech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BigTech</a> like <a href="https://mstdn.social/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a>, decide what to trust. <a href="https://www.youtube.com/watch?v=s7WDbnHlc1E" rel="nofollow noopener noreferrer" target="_blank">https://www.youtube.com/watch?v=s7WDbnHlc1E</a>Instead of <a href="https://mstdn.social/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CensorBoot</a> we would've gotten <a href="https://mstdn.social/tags/NERF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NERF</a> + <a href="https://mstdn.social/tags/Heads" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Heads</a>... But instead we get the same fundamentally unfixable bs that are <a href="https://mstdn.social/tags/CAs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CAs</a>...

Kevin Karhan :verified:<a href="https://mstdn.social/@stux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@stux</a> <a href="https://mstdn.social/tags/YecureBook" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#YecureBook</a> aka. <a href="https://mstdn.social/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CensorBoot</a> was unfixably broken with the <a href="https://mstdn.social/tags/GoldenKeyBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GoldenKeyBoot</a>.Also "client-sode encryption" one <a href="https://mstdn.social/tags/GMail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GMail</a> - like <a href="https://mastodon.social/@protonmail" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@protonmail</a> - is just a literal lie to customers: NOTHING is being encrypted at all!!!

Kevin Karhan :verified:<a href="https://comfy.social/@PeterCxy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@PeterCxy</a> +9001%<a href="https://mstdn.social/tags/TPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TPM</a> has nothing to do with <a href="https://mstdn.social/tags/Trust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Trust</a> or <a href="https://mstdn.social/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> but [and this is where <a href="https://mstdn.social/tags/Stallman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Stallman</a> is sadly true!] <a href="https://mstdn.social/tags/SecureBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecureBoot</a>'s only existance is to act as <a href="https://mstdn.social/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CensorBoot</a>, as doesn't fix <a href="https://mstdn.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> issues [as <a href="https://mstdn.social/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a> is an unfixable <a href="https://mstdn.social/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Govware</a> full of <a href="https://mstdn.social/tags/Backdoors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Backdoors</a>]...It's only meant to prevent people from using <a href="https://mstdn.social/tags/secure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#secure</a> and <a href="https://mstdn.social/tags/trustworthy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#trustworthy</a> OSes like a <a href="https://mstdn.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> distro of their choice.<a href="https://www.youtube.com/watch?v=s7WDbnHlc1E" rel="nofollow noopener noreferrer" target="_blank">https://www.youtube.com/watch?v=s7WDbnHlc1E</a>

Recent searches

Search options

Administered by:

Server stats:

#CensorBoot