| 1 |
On Fri, 3 Jul 2015 21:40:50 +0000 Robin H. Johnson wrote: |
| 2 |
> On Sat, Jul 04, 2015 at 12:19:41AM +0300, Andrew Savchenko wrote: |
| 3 |
> > As I see from git docs only commits and tags may be signed. There |
| 4 |
> > is no way to sign a push. Moreover there is no need to sign each |
| 5 |
> > commit, see what Linux says on that: |
| 6 |
> > http://git.661346.n2.nabble.com/GPG-signing-for-git-commit-td2582986.html |
| 7 |
> That was Linus's 2009 opinion, and he changed his mind since then, with |
| 8 |
> the research into further attacks on SHA1. |
| 9 |
> |
| 10 |
> Git (since 2.2) DOES support signed push. Look at the manpage for |
| 11 |
> git-push, for the --signed option: |
| 12 |
> http://git-scm.com/docs/git-push |
| 13 |
|
| 14 |
We have a rule of "one year compatibility period". ChangeLog shows |
| 15 |
that git-2.2.0 was introduced on 02 Dec 2014. So pushed commits |
| 16 |
can't be enforced before 02 Dec 2015. (And yes, my laptop |
| 17 |
still uses an older version, that's why I was unable to find --sign |
| 18 |
in the git-push manual.) |
| 19 |
|
| 20 |
Best regards, |
| 21 |
Andrew Savchenko |
Archives