If it was Star Trek, this would be the point where you're bombarded with so much gunfire that your shields drop to 6% or you have to abandon ship
But I call bullshit on that paper. Simply running an xterm or other CMD/terminal that only supports ANSI character sets will mitigate this by making the code appear to be the malicious gibberish it really is.
My recommendation is to hold all patches/pull requests until solutions/defense/shields are found !
I don't think you've maintained an open source project but if you have you would know that it is clearly impossible to do this without opening yourself up more
gunfire unpatched vulnerabilities.
If this was Star Trek hmmm.... then we would believe our shields are ON while they are OFF lol.
Trigger:
if Shield = "OFF" then Shield = "ON"
Anyway... at least you admit there is a big fat problem by switching to CMD.exe, no more project source files for you, no more fancy pancy development environment for you ! LOL.
I wonder how many bugs/hints/warning messages are missed by CMD.EXE !
CMD.EXE on Windows 7 is immune indeed, not sure about powershell on Windows 11.
Anyway have fake with your fake shields ! LOL.
Fake vaccines, now we have FAKE SHIELDS and FAKE CODE LOL ! =D
Anyway on a more serious note, GITHUB has taken some precautions which can be seen here:
https://github.com/nickboucher/trojan-source/blob/main/C/commenting-out.cand here:
https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/So not all is bad.
Github was recently purchased by Microsoft, makes me wonder... are they trying to cover up something ?
