3 ms·
Git provides us with a great deal of transparency. Here's an overview of GnuPG's committers: Werner Koch: 2677 commits over a period of 5764 days. Da
by runlevel1 13y ago
Git provides us with a great deal of transparency.
Here's an overview of GnuPG's committers:
Werner Koch: 2677 commits over a period of 5764 days.
David Shaw: 1197 commits over a period of 3807 days.
Marcus Brinkmann: 202 commits over a period of 3753 days.
NIIBE Yutaka: 53 commits over a period of 641 days.
Moritz Schulte: 39 commits over a period of 1756 days.
Timo Schulz: 29 commits over a period of 896 days.
Stefan Bellon: 21 commits over a period of 765 days.
Repo Admin: 9 commits over a period of 2634 days.
Andrey Jivsov: 8 commits over a period of 37 days.
Ben Kibbey: 6 commits over a period of 20 days.
Neal Walfield: 5 commits over a period of 1 day.
So it looks like the codebase has been touched by remarkably few hands!
This doesn't negate the need for a code review of some sort, but it does suggest that it would be difficult for an outside agent to silently introduce changes in master without the core developers noticing.
EDIT: Formatting.
- bcoates 13y agoI think the threat model the OP is worried about is a three letter agency finding an unintentional bug and keeping it for their own use. He's asking for an audit from someone we can trust to actually turn over the vulnerabilities.
- strictfp 13y agoI think it would be rather easy to infiltrate a development team, especially a geographically distributed one.
- patio11 13y agoThis is a movie plot threat. Most vulnerabilities in software are not caused by suborning one of the developers -- developers create vulnerabilities all the time without being subject to adversarial action. The adversarial actor just has to look at the software artifact created and find things about it that the original developer does not realize are true.
- unreal37 13y agoWhat about cracking the password to one of those people's Git account, and then submitting a commit without anyone knowing? What if Github is compelled by a National Security Letter to allow others to modify source files and erase the logs for those changes? What if one of those guys is the next Sabu - facing 50 years in jail unless they cooperate?
- estebank 13y agoYou realize that you cannot modify a commit's content without modifying the commit hash for every subsequent commit? Your attack would be practically impossible against a git repo.
- anotherhue 13y agoThere's a possibility that a developer acted in bad faith, for the sake of love, money, or fear. I have no reason to think that this has happened, but since it is possible, and the code is open, we can check.