From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: =?utf-8?B?4oCYY29yZS11cGRhdGVz?= =?utf-8?B?4oCZ?= merge is a squashed commit Date: Thu, 4 Aug 2016 16:05:19 -0400 Message-ID: <20160804200519.GA14007@jasmine> References: <878twd20ui.fsf@gnu.org> <20160803183911.GC11621@jasmine> <87wpjxy4ta.fsf_-_@gnu.org> <20160803211032.GA6034@jasmine> <87a8gtyntw.fsf@netris.org> <20160804082400.GA1638@solar> <87ziosyalv.fsf@netris.org> <87a8gso9p4.fsf@igalia.com> <20160804164453.GB8137@jasmine> <87a8gsmq2h.fsf@igalia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42101) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVOtb-0001A9-Gy for guix-devel@gnu.org; Thu, 04 Aug 2016 16:05:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bVOtW-0003qQ-49 for guix-devel@gnu.org; Thu, 04 Aug 2016 16:05:34 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:38018) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVOtU-0003nc-QX for guix-devel@gnu.org; Thu, 04 Aug 2016 16:05:30 -0400 Content-Disposition: inline In-Reply-To: <87a8gsmq2h.fsf@igalia.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Andy Wingo Cc: guix-devel@gnu.org On Thu, Aug 04, 2016 at 06:55:34PM +0200, Andy Wingo wrote: > On Thu 04 Aug 2016 18:44, Leo Famulari writes: > > > How would the rest of us distinguish between > > > > 1) a range of your commits with a signed HEAD > > 2) a range of your commits with a signed HEAD that you pushed after I > > pushed a commit created with `git commit --author="Andy Wingo" > > I'm not sure what the threat model here is, and surely this is mostly > because I am ignorant :) Would you mind elaborating a bit more? I admit, the example is really contrived. My point is that, as far as I know, there is no way to know who exactly is behind an unsigned Git commit. The "Author" and "Commit" information seen in `git log --format=full` is trivially forged, for example by altering the [user] field of your Git configuration file.