but you did notice that compilers can be manipulated to include backdoors into resulting binaries AND put the same manipulation into newly compiled compilers as well, right? then where did you get that compiler from? did you have a look at the binary output? then if so, did you look at it using the hexeditor of that same compiler? 😎 plz have a look … 💥 bzzzt … really you are lucky to be alive after a blast like that, especially you, have yourself checked out with ems before you leave!
does it? I got the source from coreboot.org and compiled it myself.
but you did notice that compilers can be manipulated to include backdoors into resulting binaries AND put the same manipulation into newly compiled compilers as well, right? then where did you get that compiler from? did you have a look at the binary output? then if so, did you look at it using the hexeditor of that same compiler? 😎 plz have a look … 💥 bzzzt … really you are lucky to be alive after a blast like that, especially you, have yourself checked out with ems before you leave!
I looked at it by inspecting my hdd with a microscope. is that good enough?
if it was at least a scanning tunneling one, then yes, good job 👍 🤪
Uhm… My microscopes firmware was compiled with the same compiler I used for coreboot…
yeah! you beat me to it 👍
guess this instance is lost, lets restart the matrix!
https://youtu.be/rNdpvNH1yi8?si=GPLbzrNxnwKNCfHm