Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by remram on Sunday June 20, 2021 @08:35PM
(#27575106)
That only works if you coordinate. With even more people, you can pick randomly and be relatively sure you've read it all, but I posit that 1) you don't pick randomly, you pick a part that is accessible or interesting to you (and therefore probably others) and 2) reading code locally is not sufficient to find bugs or backdoors in the whole.
[ Parent
| on HN ]
Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by pabs3 on Sunday June 20, 2021 @10:31PM
(#27575720)
The crev folks are working on a co-ordination system for incremental distributed code review:
Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by IgorPartola on Sunday June 20, 2021 @11:10PM
(#27575919)
I actually wonder if it’s possible to write code at such a macro level as to obfuscate, say, a keylogger in a huge codebase such that reviewing just a single module/unit would not reveal that something bad is going on.
Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by eru on Monday June 21, 2021 @03:42AM
(#27577127)
Depends on how complicated the project itself is. A simple structure with the bare minimum of side-effects (think, functional programming) would make this effort harder.
For something like C, all bets are off: http://www.underhanded-c.org/ or https://en.wikipedia.org/wiki/Underhanded_C_Contest