'Trojan Source' bug a novel way to attack program encodings: https://techxplore.com/news/2021-11-trojan-source-bug-encodings.html
On 21/11/03 4:06 PM, Gary Scott wrote:
'Trojan Source' bug a novel way to attack program encodings: https://techxplore.com/news/2021-11-trojan-source-bug-encodings.htmlIf "virtually all of the most popular programming languages" allow
this Unicode trick, as we read, can we conclude then that Fortran
is "virtually the only safe programming language"?!
Saved by backward compatibility with punch cards, of course! :-)
--
Jos
'Trojan Source' bug a novel way to attack program encodings: https://techxplore.com/news/2021-11-trojan-source-bug-encodings.html
On Wednesday, November 3, 2021 at 8:06:22 AM UTC-7, Gary Scott wrote:
'Trojan Source' bug a novel way to attack program encodings:
https://techxplore.com/news/2021-11-trojan-source-bug-encodings.html
There was once a story, though I don't know if it was ever implemented,
about a trojan C compiler. The compiler would compile its own source
code, and add in the trojan during compilation. You could look at the source all you wanted, and would never see it, but it would end up in the compiler anyway.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 159 |
Nodes: | 16 (0 / 16) |
Uptime: | 99:21:36 |
Calls: | 3,209 |
Files: | 10,563 |
Messages: | 3,009,786 |