All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sam Vilain <sam@vilain.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Authenticate push via PGP signature, not SSH
Date: Mon, 28 Jan 2008 21:57:43 -0500	[thread overview]
Message-ID: <20080129025743.GH24004@spearce.org> (raw)
In-Reply-To: <479E5021.7010404@vilain.net>

Sam Vilain <sam@vilain.net> wrote:
> Shawn O. Pearce wrote:
> > But in a smaller business type setting, where there's under 100
> > employees working, odds are you've already created the user account
> > on systems, and physically passed the initial password via a sticky
> > note after checking the person's government issued IDs.  In such a
> > setting having yet another authentication system (PGP keys) is just
> > yet more work for the already over worked/under appreciated IT staff.
> 
> Agreed - again I'd personally consider allowing receive-pack with
> reflogs in those environments if setting up PGP or SSH keys was a hassle.

Yea, I already have reflogs enabled for all stored branches on the
central server.  And since some branches have a no-delete policy
(based upon the rules offered by contrib/hooks/update-paranoid) the
reflogs are also effectively no-delete, even if the branch rewinds.

I also never run `git reflog expire`.  I might in another year or
so consider it, but most of my no-delete branches also don't rewind
very often (if ever) so there's very little disk to be gained by
reflog expiry.

-- 
Shawn.

  reply	other threads:[~2008-01-29  2:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28  4:12 [RFC] Authenticate push via PGP signature, not SSH Sam Vilain
2008-01-28  8:12 ` Shawn O. Pearce
2008-01-28 21:06   ` Jan Hudec
2008-01-28 21:58   ` Sam Vilain
2008-01-29  2:57     ` Shawn O. Pearce [this message]
2008-01-29  4:10     ` Shawn O. Pearce
2008-01-29 19:08       ` Pierre Habouzit
2008-01-30  4:22         ` Shawn O. Pearce
2008-01-30  5:55           ` Sam Vilain
2008-01-30  6:16             ` Shawn O. Pearce
2008-01-30  8:35             ` Pierre Habouzit
2008-01-30 20:22               ` Sam Vilain
2008-01-30  8:00           ` Johannes Sixt
2008-01-31  5:43             ` Shawn O. Pearce
2008-01-30  8:33           ` Pierre Habouzit
2008-01-31  4:30             ` Shawn O. Pearce
2008-01-31  9:25               ` Pierre Habouzit
2008-01-30  6:29       ` Sam Vilain
2008-01-30  7:47         ` Shawn O. Pearce
2008-01-31  1:18           ` Sam Vilain
2008-01-28  8:48 ` Pierre Habouzit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080129025743.GH24004@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=sam@vilain.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.