> > push for hash-agnosticity. I don't know if git-evtag is hash agnostic, > > but if it is not, then we have two transition plans to think about. > > I don't think there's even a question here: Git has to transition off > of SHA-1. > > In that context, Stefan's comment is a welcome one: once we've > transitioned off of SHA-1, having a separate evtag feature would make > git more complicated without any benefit to match. To put it another > way, the gpgsig-sha256 field described in > Documentation/technical/hash-function-transition.txt provides > essentially the same functionality as an evtag. What's missing is an > implementation of it. > > I'm happy to help in any way I can (reviews, advice, etc). Same here, although I'm a bit swamped with other work... > > > Full disclosure, I published a "competing" solution a couple of years > > ago[1] but, in my personal opinion, I think push certificates can > > achieve the same security guarantees as my system with very little > > changes. > > Work to improve the usability of push certs would also be very very > welcome. I agree. I personally think that at least the sample hook work on here would be a good candidate for this[1], although I don't know what's the status of it. The way they are right now, they should at least warn when push certificates are not enabled on the server side (i.e., there is no hook to handle it). > > Thanks and hope that helps, > Jonathan No, thanks to you :) -Santiago. [1] https://public-inbox.org/git/20171202091248.6037-1-root@xxxxxxxxxxxxxxxx/
Attachment:
signature.asc
Description: PGP signature
