From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Rorvick Subject: Re: git push tags Date: Tue, 30 Oct 2012 14:11:42 -0500 Message-ID: References: <508D7628.10509@kdbg.org> <4B8097A9D6854CDFA27E7CF6574B37BA@PhilipOakley> <508E532F.2010109@alum.mit.edu> <20121029103837.GA14614@sigill.intra.peff.net> <20121029113500.GA15597@sigill.intra.peff.net> <20121029172330.GC8359@camk.edu.pl> <20121029213508.GB20513@sigill.intra.peff.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: git To: Angelo Borsotti X-From: git-owner@vger.kernel.org Tue Oct 30 20:11:58 2012 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TTHED-0000jO-51 for gcvg-git-2@plane.gmane.org; Tue, 30 Oct 2012 20:11:57 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934221Ab2J3TLo (ORCPT ); Tue, 30 Oct 2012 15:11:44 -0400 Received: from mail-la0-f46.google.com ([209.85.215.46]:61208 "EHLO mail-la0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932654Ab2J3TLn (ORCPT ); Tue, 30 Oct 2012 15:11:43 -0400 Received: by mail-la0-f46.google.com with SMTP id h6so482362lag.19 for ; Tue, 30 Oct 2012 12:11:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=aKtzQ5aP4Sow/htNlR9QeK5g7XgO0pWGmUsE4BLmX/U=; b=doyFPIOTb3YHLhCzTwTqXdb/eFBvxgvKPfvGzUQMDX7RMhLLo9YH/ixaUeoqZxaKc0 xVXVgMo7oBNc38aUkcYivObNWiAWD5pRuS6uLuMmx2TBi1UU2nAmXnWFHfctHCTrFKnl H7HZl1uAc4HFdQGZIoSw82Fv26ZR4dgVF4I0tHSEp3pI8KwFGf59qe5xMBqfk3zakMZB R9rW3MBJc8D4z74k8POxwRu8ggkCwngZvGQ2j9fXqxbviCUISAl3LUYc2QQUHmFSMqeZ FY7Mb2A974kViQX8ofZ7hQVlq16y7L/0hoj0VwgDh/hWOaVJ1QX41a/2CCmozl5VLPp3 mc4w== Received: by 10.112.14.107 with SMTP id o11mr13609456lbc.98.1351624302192; Tue, 30 Oct 2012 12:11:42 -0700 (PDT) Received: by 10.114.2.45 with HTTP; Tue, 30 Oct 2012 12:11:42 -0700 (PDT) In-Reply-To: X-Google-Sender-Auth: zgG-toPW58HJoIih0rn71PvWGNw Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Tue, Oct 30, 2012 at 1:34 PM, Angelo Borsotti wrote: > Hi Cris, > > I think a key in the config file of the remote repo is better than an > option on git-push for what concerns security: it allows the owner of > the remote repo to enforce the policy not to overwrite tags, which > would not be possible if any user that has push access can --force > tags. > > -Angelo Hi Angelo, Security is orthogonal to what this patch is attempting to resolve. As Kacper pointed out, you can never be sure you're not going to clobber an existing tag in the remote repo. This patch attempts to give git-push better (i.e., less surprising) semantics for tags. In other words, it's should will prevent mistakes, not provide any sort of security. So I don't think a config option is better or worse, it's just trying to solve a different problem. Thanks, Chris