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:

284
active users

#microcode

1 post1 participant0 posts today
Ian Brown 👨🏻‍💻<p>In fact, governments probably should only EVER deploy executables they have built themselves, using their own compilers (see the classic computer science paper Reflections on Trusting Trust). </p><p>You’d also need chip <a href="https://eupolicy.social/tags/microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>microcode</span></a> auditing and verification for security-critical systems. And some level of chip assurance. And 🇬🇧 Cell-like audits… Details to be determined 😉</p><p><a href="https://eupolicy.social/tags/ReproducibleBuilds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReproducibleBuilds</span></a><br> <a href="https://eupolicy.social/tags/StrategicAutonomy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>StrategicAutonomy</span></a> <a href="https://eupolicy.social/tags/audit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>audit</span></a> <a href="https://eupolicy.social/tags/escrow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>escrow</span></a></p>
boredsquirrel<p><span class="h-card" translate="no"><a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nixCraft</span></a></span> </p><p><a href="https://tux.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NixOS</span></a> is interesting. Pretty reliable (not as much as <a href="https://tux.social/tags/AtomicDesktops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AtomicDesktops</span></a> in my noob tests) while also performant</p><p>Note that such old hardware will have <a href="https://tux.social/tags/microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>microcode</span></a> vulnerabilities and locking it down will further slow it down. At least thinking of <a href="https://tux.social/tags/spectre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spectre</span></a> or <a href="https://tux.social/tags/meltdown" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meltdown</span></a> (not sure if hyperthreading was even thought of back then)</p>
SpaceLifeForm<p>Old man yells at clouds </p><p>4, 4, 4, 4, ...</p><p><a href="https://m.slashdot.org/story/438589" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">m.slashdot.org/story/438589</span><span class="invisible"></span></a></p><p><a href="https://infosec.exchange/tags/MicroCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MicroCode</span></a></p>
SpaceLifeForm<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@chandlerc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>chandlerc</span></a></span> </p><p>So, does this imply that it is a failure by the software to not realize that the hardware and microcode have made a mistake?</p><p>There is a lot that can be done at the software level, but to do that still requires that the machine code instructions still function as expected.</p><p>It is turtles all of the way down.</p><p><a href="https://infosec.exchange/tags/Infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Infosec</span></a> <a href="https://infosec.exchange/tags/microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>microcode</span></a> <a href="https://infosec.exchange/tags/leak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>leak</span></a></p>
SpaceLifeForm<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@chandlerc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>chandlerc</span></a></span> </p><p>The domain name is accurate.</p><p><a href="https://infosec.exchange/tags/Infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Infosec</span></a> <a href="https://infosec.exchange/tags/Microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microcode</span></a> <a href="https://infosec.exchange/tags/Leak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Leak</span></a></p>
SpaceLifeForm<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@chandlerc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>chandlerc</span></a></span> </p><p>Speculative Executation is not your friend.</p><p><a href="https://infosec.exchange/tags/Infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Infosec</span></a> <a href="https://infosec.exchange/tags/Microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microcode</span></a> <a href="https://infosec.exchange/tags/Leak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Leak</span></a></p>
SpaceLifeForm<p><span class="h-card" translate="no"><a href="https://mastodon.scot/@kim_harding" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>kim_harding</span></a></span> </p><p>Speculative Executation again. See Spectre, et al.</p><p>If only I could run a modern browser on a Pentium.</p><p><a href="https://infosec.exchange/tags/Infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Infosec</span></a> <a href="https://infosec.exchange/tags/Microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microcode</span></a> <a href="https://infosec.exchange/tags/Leak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Leak</span></a></p>
IT News<p>This Week in Security: ClamAV, The AMD Leak, and The Unencrypted Power Grid - Cisco’s ClamAV has a heap-based buffer overflow in its OLE2 file scanning. That’s ... - <a href="https://hackaday.com/2025/01/24/this-week-in-security-clamav-the-amd-leak-and-the-unencrypted-power-grid/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2025/01/24/this-w</span><span class="invisible">eek-in-security-clamav-the-amd-leak-and-the-unencrypted-power-grid/</span></a> <a href="https://schleuss.online/tags/thisweekinsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>thisweekinsecurity</span></a> <a href="https://schleuss.online/tags/hackadaycolumns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hackadaycolumns</span></a> <a href="https://schleuss.online/tags/securityhacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>securityhacks</span></a> <a href="https://schleuss.online/tags/pentesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentesting</span></a> <a href="https://schleuss.online/tags/microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>microcode</span></a> <a href="https://schleuss.online/tags/clamav" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>clamav</span></a> <a href="https://schleuss.online/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>news</span></a></p>
Kevin Karhan :verified:<p>Yes. <a href="https://www.tomshardware.com/pc-components/cpus/intel-engineers-linux-patch-would-alert-users-of-outdated-microcode-flagging-the-system-as-vulnerable" rel="nofollow noopener noreferrer" target="_blank">this</a> is a good thing for <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ITsec</span></a> to let end-users know if their system runs <a href="https://infosec.space/tags/outdated" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>outdated</span></a> / <a href="https://infosec.space/tags/vulnerable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vulnerable</span></a> <a href="https://infosec.space/tags/Microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microcode</span></a> <em>and</em> have <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> update it.</p><ul><li>OFC this can't fix the systemic issues <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ix86</span></a> &amp; <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amd64</span></a> have, but I do think this is such a vital thing that I do want to integrate it into <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>OS1337</span></a></span> as having some low-level diagnostics and means to fix things is literally the point of said distro!</li></ul><p>Consider it a more streamlined "Rescue Linux" which is intended to be <a href="https://infosec.space/tags/reprpduceable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>reprpduceable</span></a>, <a href="https://infosec.space/tags/auditable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>auditable</span></a> and small enough to fit on a <a href="https://infosec.space/tags/BootROM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BootROM</span></a>! </p><p><a href="https://infosec.space/tags/Intel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Intel</span></a> <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ITsec</span></a> <a href="https://infosec.space/tags/Updates" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Updates</span></a></p>
IT News<p>Custom Microcode Compiler, Made in Google Sheets - When homebrewing a CPU, one has to deal with microcode. Microcode is the low-level... - <a href="https://hackaday.com/2024/07/07/custom-microcode-compiler-made-in-google-sheets/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2024/07/07/custom</span><span class="invisible">-microcode-compiler-made-in-google-sheets/</span></a> <a href="https://schleuss.online/tags/classiccomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>classiccomputing</span></a> <a href="https://schleuss.online/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>retrocomputing</span></a> <a href="https://schleuss.online/tags/softwarehacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>softwarehacks</span></a> <a href="https://schleuss.online/tags/homebrewcpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homebrewcpu</span></a> <a href="https://schleuss.online/tags/microcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>microcode</span></a> <a href="https://schleuss.online/tags/cpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cpu</span></a></p>

#Intel Deploys Undisclosed #Microcode Security Update For CPUs Going Back To Coffee Lake (2017 launched CPUs)

Intel released CPU microcode updates for processors all the way back to Coffee Lake on Friday afternoon. Unfortunately, the changelog doesn't delve into details other than that the new microcode fixes an undisclosed security issue.

#InfoSec
tomshardware.com/news/intel-mi

Tom's HardwareIntel Deploys Undisclosed Microcode Security Update For CPUs Going Back To Coffee LakeBy Zhiye Liu