▲ 325 ▼ Ken Thompson Hack 2.0 (thelemmy.club) submitted 2 weeks ago by einfach_orangensaft@sh.itjust.works to c/linuxmemes@lemmy.world 94 comments fedilink hide all child comments
[–] bacon_pdp@lemmy.world 6 points 2 weeks ago (1 child) They already have a solution to the Trusting trust attack thanks to DDC and live-bootstrap’s work. https://guix.gnu.org/en/blog/2023/the-full-source-bootstrap-building-from-source-all-the-way-down/ permalink fedilink source hideshow 2 child comments replies: [–] Natanox@discuss.tchncs.de 3 points 2 weeks ago (1 child) Mmh… but this concept only fully works on Open-Source hardware, doesn't it? Otherwise the microcode or CPU itself could still be an attack vector to infect the bootstrapped compiler? (Genuinely curious, I have no clue) permalink fedilink source parent hideshow 2 child comments replies: [–] bacon_pdp@lemmy.world 0 points 2 weeks ago That would be the deeply classified Nexus Intruder Program that no one has yet solved. Which would be hardware that infects software that in turn infects the next generation of hardware. permalink fedilink source parent
[–] Natanox@discuss.tchncs.de 3 points 2 weeks ago (1 child) Mmh… but this concept only fully works on Open-Source hardware, doesn't it? Otherwise the microcode or CPU itself could still be an attack vector to infect the bootstrapped compiler? (Genuinely curious, I have no clue) permalink fedilink source parent hideshow 2 child comments replies: [–] bacon_pdp@lemmy.world 0 points 2 weeks ago That would be the deeply classified Nexus Intruder Program that no one has yet solved. Which would be hardware that infects software that in turn infects the next generation of hardware. permalink fedilink source parent
[–] bacon_pdp@lemmy.world 0 points 2 weeks ago That would be the deeply classified Nexus Intruder Program that no one has yet solved. Which would be hardware that infects software that in turn infects the next generation of hardware. permalink fedilink source parent
