lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 17 Jan 2012 17:47:15 -0800
From:	Junio C Hamano <gitster@...ox.com>
To:	Andrew Ardill <andrew.ardill@...il.com>
Cc:	git@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Using signed tag in pull requests

Andrew Ardill <andrew.ardill@...il.com> writes:

>> Starting from Git release v1.7.9, a contributor can add a signed tag to
>> the commit at the tip of the history and ask the integrator to pull that
>> signed tag. When the integrator runs `git pull`, the signed tag is
>> automatically verified to assure that the history is not tampered with.
>> In addition, the resulting merge commit records the content of the signed
>> tag, so that other people can verify that the branch merged by the
>> contributor was signed by the contributor, without fetching the signed tag
>
> I think you mean to say 'the branch merged by the integrator was signed
> by the contributor'.

Definitely. I'll update my local copy.

Thanks for spotting this.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ