Dice.camp

Kevin Karhan :verified:<a href="https://t3n.social/@t3n" class="u-url mention" rel="nofollow noopener" target="_blank">@t3n</a> nicht wirklich ungewiss:<a href="https://infosec.space/tags/BestCase" class="mention hashtag" rel="nofollow noopener" target="_blank">#BestCase</a>: Leute lassen sich nicht von <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> verarschen, werweigern sivh <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> und schauen uaf <a href="https://endof10.org" rel="nofollow noopener" translate="no" target="_blank">https://endof10.org</a> nach Alternativen.Wacheinlichstes Szenario: Tausende Tonnen 100% vermeidbarer <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> wird generiert aber die allermeisten System kommen billig in den Gebrauchtmarkt.<a href="https://infosec.space/tags/WorstCase" class="mention hashtag" rel="nofollow noopener" target="_blank">#WorstCase</a>: Tausende Tonnen 100% vermeidbarer <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> wird generiert!

Kevin Karhan :verified:<a href="https://myside-yourside.net/@StarkRG" class="u-url mention" rel="nofollow noopener" target="_blank">@StarkRG</a> I agree and I do the same.<ul><li>It's just gotten so bad that I know companies are literally willing to pay <a href="https://infosec.space/tags/IdiotTax" class="mention hashtag" rel="nofollow noopener" target="_blank">#IdiotTax</a> and trash perfectly fine hardware because <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> like <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a> can't do <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> and/or 8 GB RAM are not enough if you want to use more than 2 messengers at the time and still have like a ticketing system, wiki, softphone and eMail client open (aka. <a href="https://infosec.space/tags/TechSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechSupport</a>)…</li></ul>

Kevin Karhan :verified:<a href="https://chaos.social/@LaF0rge" class="u-url mention" rel="nofollow noopener" target="_blank">@LaF0rge</a> <a href="https://mastodon.social/@sysmocom" class="u-url mention" rel="nofollow noopener" target="_blank">@sysmocom</a> granted, I do trust the GSMA more than Beijing, but that's more due to the fact that conflicting desires if GSMA members tend to be harder to steer.<ul><li>Similarly GAFAMs conflicting ideas prevented them from enshittifying Linux.</li></ul>Still, I think that end users and device integrators should have full control over the certificates and root of trust, including the ability to add alternative Root-CAs and even removing GSMA's Root-CA (similar to how "Secure Boot" should've been done instead of <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a>!) <ul><li>Whether it would be a wise decision to yeet the GSMA cert is a different story, but given what I know in terms of "security" I'd certainly not trust <a href="https://infosec.space/tags/Bundesdruckerei" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bundesdruckerei</a> and it's subsidiaries to be competent.</li></ul>Certainly being able to exercise full control would make a lot of <a href="https://infosec.space/tags/osmocom" class="mention hashtag" rel="nofollow noopener" target="_blank">#osmocom</a>'s development easier.

Kevin Karhan :verified:<a href="https://friendica.a-zwenkau.de/profile/franky" class="u-url mention" rel="nofollow noopener" target="_blank">@franky</a> <a href="https://bonn.social/@ulrichkelber" class="u-url mention" rel="nofollow noopener" target="_blank">@ulrichkelber</a> <a href="https://sueden.social/@kontrollierterWahnwitz" class="u-url mention" rel="nofollow noopener" target="_blank">@kontrollierterWahnwitz</a> es heißt <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a>, denn <a href="https://infosec.space/tags/HoldenKeyBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#HoldenKeyBoot</a> macht "<a href="https://infosec.space/tags/SecureBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecureBoot</a>" unfixable unsicher!

Kevin Karhan :verified:<a href="https://mastodon.social/@mrgrumpymonkey" class="u-url mention" rel="nofollow noopener" target="_blank">@mrgrumpymonkey</a> it is.One can repartition Windows installations on the fly whilst running (and even then there are tools like <a href="https://infosec.space/tags/Wubi" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wubi</a> that made it easy to setup <a href="https://infosec.space/tags/dualboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#dualboot</a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> & <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>.<ul><li>ISOLINUX does allow for "load image into RAM and boot" setups. I literally use that on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> because no system that can boot it will have > 16 MB RAM anyway ( 8 MB is the hard limit for bare linux kernel) so merely making Windows' bootloader to chainload <a href="https://infosec.space/tags/isolinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#isolinux</a> to load that image in RAM and yeet it isn't out of the question.</li></ul>I just have neither a <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> machine nor time and spoons to make such a tool, much less to basically create even said <a href="https://infosec.space/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> "<a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a>"…<ul><li>But thanks to <a href="https://infosec.space/tags/GoldenKeyBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#GoldenKeyBoot</a>, <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> is unfixably insecure!</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@mrgrumpymonkey" class="u-url mention" rel="nofollow noopener" target="_blank">@mrgrumpymonkey</a> better even if you can build a <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> that automagically installs <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> over a <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a>'ed <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a>!

Kevin Karhan :verified:<a href="https://chaos.social/@Cheatha" class="u-url mention" rel="nofollow noopener" target="_blank">@Cheatha</a> nodds in agreementKeep the envoirment safe, ditch <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> & <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a>!<a href="https://enof10.org" rel="nofollow noopener" translate="no" target="_blank">https://enof10.org</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@itsfoss" class="u-url mention" rel="nofollow noopener" target="_blank">@itsfoss</a> nodds in agreement the amount of <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> creates is s absurd, it'll make hee <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> converting to <a href="https://infosec.space/tags/IEC60906_1" class="mention hashtag" rel="nofollow noopener" target="_blank">#IEC60906_1</a> look like envoirmentally responsible by comparison. <ul><li>OFC <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> didn't do that citing 700.000t of <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> as argument against it.</li></ul>I wounder how many millions of PCs get replaced for no good reason because Microsofts's new <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> requires <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a>! <a href="https://en.wikipedia.org/wiki/IEC_60906-1" rel="nofollow noopener" translate="no" target="_blank">https://en.wikipedia.org/wiki/IEC_60906-1</a>

Kevin Karhan :verified:<a href="https://blob.cat/users/Jain" class="u-url mention" rel="nofollow noopener" target="_blank">@Jain</a> <a href="https://brotka.st/users/kaia" class="u-url mention" rel="nofollow noopener" target="_blank">@kaia</a> +9001%Liegt eher an <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a>!

Kevin Karhan :verified:<a href="https://eupolicy.social/@jmaris" class="u-url mention" rel="nofollow noopener" target="_blank">@jmaris</a> <a href="https://floss.social/@kde" class="u-url mention" rel="nofollow noopener" target="_blank">@kde</a> I think getting rid of <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> is the correct approach.<ul><li><a href="https://infosec.space/tags/EndOf10" class="mention hashtag" rel="nofollow noopener" target="_blank">#EndOf10</a> should also mark the end of <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a> and a ban of <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> for creating thousands of tons of 100% avoidable <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> due to <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a>.</li></ul>

Kevin Karhan :verified:<a href="https://mk.moth.zone/@eri" class="u-url mention" rel="nofollow noopener" target="_blank">@eri</a> worse even is the <a href="https://infosec.space/tags/EoL" class="mention hashtag" rel="nofollow noopener" target="_blank">#EoL</a> of <a href="https://infosec.space/tags/Winfows10" class="mention hashtag" rel="nofollow noopener" target="_blank">#Winfows10</a> and <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> mandating <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> for <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a>, thus generating.thousands of tons of 100% avoidable <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> in return!

Kevin Karhan :verified:<a href="https://m.ai6yr.org/@ai6yr" class="u-url mention" rel="nofollow noopener" target="_blank">@ai6yr</a> and guess what: <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> caused this issue by mandating <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> via <a href="https://infosec.space/tags/TPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#TPM</a> 2.0 for no valid reason.<ul><li>This is an <a href="https://infosec.space/tags/EnvoirmentalCrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#EnvoirmentalCrime</a> and they should be forced to undo the harm caused!</li></ul>

Kevin Karhan :verified:<a href="https://mk.absturztau.be/@Eyedust" class="u-url mention" rel="nofollow noopener" target="_blank">@Eyedust</a> <a href="https://infosec.space/@topher" class="u-url mention" rel="nofollow noopener" target="_blank">@topher</a> exactly that is my main gripe.The reason the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> refused to standardize upon <a href="https://en.wikipedia.org/wiki/IEC_60906-1#Possibility_of_acceptance_in_European_Union" rel="nofollow noopener" target="_blank">IEC 60906-1</a> was because they expected it to generate 700.000t of 100% avoidable <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> (or ~ 1,4 kg per EU citizen).<ul><li>IDK about you, but even if people were to only throw out mainboards due to <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> (which noone does!) we'd easily see way more eWaste due to <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a> in the EU alone, yet <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> and <a href="https://social.bund.de/@Bundesregierung" class="u-url mention" rel="nofollow noopener" target="_blank">@Bundesregierung</a> don't even bat an eye.</li></ul>And that really infuriates me like this:

Kevin Karhan :verified:<a href="https://infosec.space/@topher" class="u-url mention" rel="nofollow noopener" target="_blank">@topher</a> the problem is the <a href="https://infosec.space/tags/Enshittifiaction" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittifiaction</a> and <a href="https://infosec.space/tags/Enfattening" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enfattening</a> of <a href="https://infosec.space/tags/Websites" class="mention hashtag" rel="nofollow noopener" target="_blank">#Websites</a> and <a href="https://infosec.space/tags/Applications" class="mention hashtag" rel="nofollow noopener" target="_blank">#Applications</a>! Seriously, I think that <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> should be sued into insolvency for the way they create 100% avoidable <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> with <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> and <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a> to the point that if I didn't have my current job, I'd basically collect all the old machines from companies that are stupid enough to use <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> [and they'll likely give them away for free minus SSDs / HDDs instead of paying €5+ for <a href="https://infosec.space/tags/recycling" class="mention hashtag" rel="nofollow noopener" target="_blank">#recycling</a>], shove some <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> on [i.e. <a href="https://infosec.space/tags/RaspberryPiOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPiOS</a>, <a href="https://infosec.space/tags/BunsenLabsLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#BunsenLabsLinux</a> or <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#UbuntuLTS</a>] and sell those off as used electronics for a good profit.

Kevin Karhan :verified:<a href="https://transfem.social/@puppygirlhornypost2" class="u-url mention" rel="nofollow noopener" target="_blank">@puppygirlhornypost2</a> <a href="https://social.vlhl.dev/users/navi" class="u-url mention" rel="nofollow noopener" target="_blank">@navi</a> nodds in agreement the entire <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a>-Stack is literally done to maximize pain and frustration, brick <a href="https://infosec.space/tags/DualBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualBoot</a> / <a href="https://infosec.space/tags/MultiBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#MultiBoot</a> setups and is by <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a>'s <a href="https://www.youtube.com/watch?v=U7VwtOrwceo&t=11m10s" rel="nofollow noopener" target="_blank">own admission inherently & unfixably insecure</a>.<ul><li>As can be seen by the fact that they literally didn't even bother with "<a href="https://infosec.space/tags/SecureBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecureBoot</a>" on the <a href="https://infosec.space/tags/XboxOne" class="mention hashtag" rel="nofollow noopener" target="_blank">#XboxOne</a> which remains uncracked to this day...</li></ul>

Kevin Karhan :verified:<a href="https://hachyderm.io/@lucasmz" class="u-url mention" rel="nofollow noopener" target="_blank">@lucasmz</a> yes and no..<ul><li>Yes in that one can just revoke said keys and deploy one's own!</li><li>No if you can't revoke the preset <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> keys in your <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#UEFI</a>.</li><li>No in that these keys are default and that any revocation is 100% reversibe AFAICT.</li><li>No in that this would brick <a href="https://infosec.space/tags/Windows10" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows10</a>, <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a> and even some <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> install media.</li></ul>Personally I'd wish for <a href="https://infosec.space/tags/heads" class="mention hashtag" rel="nofollow noopener" target="_blank">#heads</a> and <a href="https://infosec.space/tags/PGO" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGO</a> <a href="https://infosec.space/tags/SelfSigned" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfSigned</a> code to be the norm providing the user/owner with full control over what is executeable!

Kevin Karhan :verified:<a href="https://mastodon.social/@brouhaha" class="u-url mention" rel="nofollow noopener" target="_blank">@brouhaha</a> <a href="https://infosec.exchange/@catsalad" class="u-url mention" rel="nofollow noopener" target="_blank">@catsalad</a> yeah, <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> is really keen on forxing <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> down everyones throat despite <a href="https://www.youtube.com/watch?v=U7VwtOrwceo&t=12m" rel="nofollow noopener" target="_blank">publicly admitting</a> that <a href="https://infosec.space/tags/TPM" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#XboxOne</a>!</li></ul>

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

Kevin Karhan :verified:<a href="https://eightpoint.app/@JenWithGravy" class="u-url mention" rel="nofollow noopener" target="_blank">@JenWithGravy</a> <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> was already irrevocably fucked when <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> lost the <a href="https://infosec.space/tags/PrivateKeys" class="mention hashtag" rel="nofollow noopener" target="_blank">#PrivateKeys</a> for that.<ul><li><a href="https://infosec.space/tags/GoldenKeyBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#GoldenKeyBoot</a> basically means all "<a href="https://infosec.space/tags/SecureBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecureBoot</a>" is unfixably insecure!</li></ul>And Microsoft admitted to that <a href="https://infosec.space/tags/insecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#insecurity</a> with the <a href="https://infosec.space/tags/XboxOne" class="mention hashtag" rel="nofollow noopener" target="_blank">#XboxOne</a>'s design in their own words! <a href="https://youtu.be/U7VwtOrwceo&t=663" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/U7VwtOrwceo&t=663</a><a href="https://infosec.space/tags/TLDW" class="mention hashtag" rel="nofollow noopener" target="_blank">#TLDW</a>: Don't trust any <a href="https://infosec.space/tags/blackbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#blackbox</a> to do what it claims to do!

Kevin Karhan :verified:<a href="https://mastodon.social/@Cappyjax" class="u-url mention" rel="nofollow noopener" target="_blank">@Cappyjax</a> <a href="https://chaos.social/@necrosis" class="u-url mention" rel="nofollow noopener" target="_blank">@necrosis</a> Even then it would not have resulted in machines basically self-<a href="https://infosec.space/tags/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#ransomware</a>'ing and making data recovery impossible - and even if someone were to use <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> on <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> (plz don't!) it would be faster and easier to reproducibly setup a machine from scratch and restore a backup.<ul><li>In fact, I did precisely that with a payment processor's frontend + backend and documented that in a reproducible fashion.</li></ul>OFC, <a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrowdStrike</a> lays bare not just <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>'s issues but most importantly the affected organizations "<a href="https://infosec.space/tags/TechDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechDebt</a>" and lack of <a href="https://infosec.space/tags/contingencies" class="mention hashtag" rel="nofollow noopener" target="_blank">#contingencies</a> to cold-start & rebuild their organization's <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> from scratch if need be, which is unnecessarily complex and.slow with Windows compared to any Linux distro!

Recent searches

Search options

Administered by:

Server stats:

#CensorBoot