33
Unsigned Commits
(blog.glyph.im)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Jan 2024
33 points (88.4% liked)
Programming
16971 readers
343 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Can someone explain this article? I'm not sure what signing a commit is. If it's the information appended with a commit (username, time of commit, commit message), then it sounds insane to be against that. It's so helpful to not only know who did what in case you need to reach out to the person behind something, but also knowing the why behind it can be important.
The majority of the issues the author has seem strange to me. I can understand not wanting GitHub to be this central authority. However, in what world is making a commit to a repo indicative of one endorsing every single line in a repo? And the security issues just come down to "don't let your data leak". Though that could be an issue if GitHub leaks it themselves.
it's not that, it's the cryptographic signature of the commit's contents with a private key, which allows verifiers to attest the integrity of the commit and authorship through the corresponding public key. The problem is that anyone can write anyone else's name and address in the author field. The signature would mitigate this impersonation problem.
And ultimately, that's a good thing. The article just puts into question the overall usefulness of it and how GitHub in particular handles this process.
Thank you for explaining and for the article, that makes sense. I can't see any reason against having it, but I've never had to interact with that so I'm not qualified enough to form a concrete opinion!