2 ms·
I am not really convinced. First, HTTPS is here to authenticate the server to all users, because it is important that no user wrongly believes that it connecte
by palata 3y ago
I am not really convinced.
First, HTTPS is here to authenticate the server to all users, because it is important that no user wrongly believes that it connected to the website it wanted. Many times it does not matter (e.g. a random blog), but when it does matter, it does matter for all users. Git signing is different: if I sign my commit, I really don't care if whoever runs it checked my signature; I sign it so that someone who cares (and knows what it means) can check it.
Second, I don't see the lock-in with GitHub. Signing a commit is not about getting a "verified" badge, and the public key is not limited to GitHub. On the contrary, because the signature goes with the patch, I would say it really does not depend on GitHub at all. GitHub showing information about it does not make GitHub own it.
Third, I don't get the comparison with the paper signature either: my signature on a document has some kind of legal meaning, so I won't just put it everywhere "just in case". My PGP signature doesn't: I am pretty sure I can even PGP-sign a contract document (e.g. the *.pdf) and it won't be equivalent to me writing my signature next to my name. Of course it can prove that I did PGP-sign that document, so in the case of a highly illegal document that I should not link myself to, probably I should not PGP-sign it.