Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

264
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.2

#linuxboot

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://possum.city/@tauon" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tauon</span></a></span> <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> did!</p><ul><li>That's why they pushed for <a href="https://infosec.space/tags/CensirBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CensirBoot</span></a>!</li></ul><p>IMHO <a href="https://infosec.space/tags/USEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>USEFI</span></a> is an irredeemabke <a href="https://infosec.space/tags/Bloatware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bloatware</span></a> and needs to be replaced with <a href="https://infosec.space/tags/LinuxBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxBoot</span></a> aka. <a href="https://infosec.space/tags/NERF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NERF</span></a>!</p><p><a href="https://en.wikipedia.org/wiki/LinuxBoot" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">en.wikipedia.org/wiki/LinuxBoot</span><span class="invisible"></span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.io/@wolf480pl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>wolf480pl</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@cas" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cas</span></a></span> I just assume they don't want to have to deal with a <a href="https://infosec.space/@kkarhan/114465885276391701" rel="nofollow noopener" target="_blank">gazillion of undocumented SBCs</a> that may only get 1 person to once push code that gets accepted, but then <em>"orphaned"</em> and break over time as they may not be willing to build &amp; test every new kernel before release just to enshure it ain't broken!</p><ul><li>Espechally since <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM</span></a> doesn't have just a <code>bootcode.bin</code> and <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a> to boot from, but half a dozen different mechanisms ranging from fixed sector location and -sizes for the <code>initramfs</code> to <a href="https://infosec.space/tags/uBOOT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uBOOT</span></a> &amp; <a href="https://infosec.space/tags/LinuxBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxBoot</span></a>, <a href="https://infosec.space/tags/Coreboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coreboot</span></a> and potentially even <a href="https://infosec.space/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenFirmware</span></a>-style <a href="https://infosec.space/tags/bootcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bootcode</span></a>...<br></li></ul><p>It's absolute chaos and one of the reasons I didn't even try to build <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> for the <a href="https://infosec.space/tags/Pi0W" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pi0W</span></a> as of today...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@BleepingComputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>BleepingComputer</span></a></span> pretty shure <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> supoort is more of an <a href="https://infosec.space/tags/accident" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accident</span></a>, but eother way it clearly shows the problem that <a href="https://infosec.space/tags/overcomplex" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>overcomplex</span></a> garbage like <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a> has.</p><ul><li>The solution is to swutch over to <a href="https://infosec.space/tags/LinuxBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxBoot</span></a> nee. <a href="https://infosec.space/tags/NERF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NERF</span></a> instead!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.space/@wravoc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>wravoc</span></a></span> IMHO, <a href="https://infosec.space/tags/TPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TPM</span></a> &amp; <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a> are both <a href="https://infosec.space/tags/Scams" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scams</span></a> and neither can be trusted due to being <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>backdoored</span></a> and <a href="https://infosec.space/tags/Bloatware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bloatware</span></a> respectably.</p><p>Personally, I want a machine that is purposefully <a href="https://infosec.space/tags/incompatible" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incompatible</span></a> with <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CensorBoot</span></a> by <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> (and thus <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows11</span></a>) by using <a href="https://infosec.space/tags/LinuxBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxBoot</span></a> / <a href="https://infosec.space/tags/NERF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NERF</span></a> and no TPM at all!</p><p>Sadly I guess that means I've to use the <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RISCv</span></a> version of the <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> mainboard for that...</p> <p>The fact that UEFI has more code than the <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://infosec.space/tags/Kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernel</span></a> with all it's drivers yet less than 100 contributors makes it inacceptable!</p>
Daniel 黄法官 CyReVolt 🐢<p>I am happy to announce <a href="https://mastodon.social/tags/Fiedka" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fiedka</span></a> the <a href="https://mastodon.social/tags/firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>firmware</span></a> editor v1.3.4 🥳</p><p>Now with a nice welcome screen, toolbar, CBFS (coreboot) parsing and <a href="https://mastodon.social/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a> editing capabilities. You can remove DXEs, and if space allows, replace BdsDxe with your own app to roll out <a href="https://linuxboot.org" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="">linuxboot.org</span><span class="invisible"></span></a> via the <a href="https://mastodon.social/tags/LinuxBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxBoot</span></a> button. Someone has already done that on real hardware, as I heard. \o/</p><p>Download and more information: <a href="https://fiedka.app" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="">fiedka.app</span><span class="invisible"></span></a> 🐙</p><p>PS.: Progress on the AMD PSP analysis is also happening (see screenshot). :-)</p>
TrendingLive feeds
About