51 ms·
Sounds intriguing but I'm missing the deep technical info on how it works. > All data you push is signed by your device's private key, which never leaves your
by hdhzy 9y ago
Sounds intriguing but I'm missing the deep technical info on how it works.
> All data you push is signed by your device's private key, which never leaves your device.
For the reference git already supports signed pushes (git push --signed): https://github.com/git/git/commit/a85b377d0419a9dfaca8af2320cc33b051cbed04 https://github.com/git/git/commit/a85b377d0419a9dfaca8af2320...
- welder 9y agoSigning a commit does not encrypt that commit's contents, just adds a signature to prove you wrote that commit. From the Keybase FAQ: > So is this signing my commits? > No, this is happening at a lower level, (1) to allow encryption, and (2) to ensure no unsigned or unencrypted data makes it in. Intuitively you can think of it as you and your teammates using a cryptographic secure storage layer for your git origin that doesn't really understand git. > Your commits themselves are untouched from git's perspective, so if you mirror your repository elsewhere, it'll be a regular checkout.
- hdhzy 9y agoI did not mention signing commits but signing push requests and that was a reference to: > All data you push is signed by your device's private key, which never leaves your device.