summaryrefslogtreecommitdiff
path: root/builtin/send-pack.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-08-21 23:45:30 (GMT)
committerJunio C Hamano <gitster@pobox.com>2014-09-17 21:27:40 (GMT)
commitb89363e4a5277038629491f8765c0598f366326c (patch)
tree254c02373450167a86f33afdeac9cd851859ca00 /builtin/send-pack.c
parent9be89160e7382a88e56a02bcf38f4694dd6542d6 (diff)
downloadgit-b89363e4a5277038629491f8765c0598f366326c.zip
git-b89363e4a5277038629491f8765c0598f366326c.tar.gz
git-b89363e4a5277038629491f8765c0598f366326c.tar.bz2
signed push: fortify against replay attacks
In order to prevent a valid push certificate for pushing into an repository from getting replayed in a different push operation, send a nonce string from the receive-pack process and have the signer include it in the push certificate. The receiving end uses an HMAC hash of the path to the repository it serves and the current time stamp, hashed with a secret seed (the secret seed does not have to be per-repository but can be defined in /etc/gitconfig) to generate the nonce, in order to ensure that a random third party cannot forge a nonce that looks like it originated from it. The original nonce is exported as GIT_PUSH_CERT_NONCE for the hooks to examine and match against the value on the "nonce" header in the certificate to notice a replay, but returned "nonce" header in the push certificate is examined by receive-pack and the result is exported as GIT_PUSH_CERT_NONCE_STATUS, whose value would be "OK" if the nonce recorded in the certificate matches what we expect, so that the hooks can more easily check. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/send-pack.c')
0 files changed, 0 insertions, 0 deletions