11
Why would you want to sign your commits with PGP? Is SSH insufficient? (programming.dev)
submitted 1 year ago by to c/cybersecurity@sh.itjust.works
6 comments fedilink hide all child comments
 

So, feel free to correct me if I am wrong but this is my current knowledge about ts:

  1. PGP and SSH both use asymmetric encryption; in other words there is always a public and private key.
  2. You can verify the sender with your public key if the sender signs whatever he sends with his private key.
  3. You tend to insert your public key into remote Git repository like Github etc.

So should your private key not be sufficient to verify your identity when you push commits? Why would you want to use PGP instead?

you are viewing a single comment's thread
view the rest of the comments
[–] -1 points 1 year ago

Ssh is for getting the code to the repository securely. While it is part of making sure the code doesn't change when it transit, nothing it does stays with the code after that.

PGP is for signing the code. The PGP signature is baked into the repo history itself as a part of the commit. Because it stays with the code, it provides a way to record that someone is signing off on a specific set of changes. Additionally, because it is a signature it also allows verification that the change that was signed off on has not been modified in the repository.

  • permalink
  • fedilink
  • source
    •