List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: your mail
Date: Sun, 23 Jul 2017 13:00:19 +0100	[thread overview]
Message-ID: <20170723120019.GK1600@john.keeping.me.uk> (raw)
In-Reply-To: <CAGveaD7+RRwk7L-b9m3MCxokvLy7Yn6Tsw44zpOx0fDPqyYHVQ@mail.gmail.com>

[Please keep the mailing list cc'd.]

On Sat, Jul 22, 2017 at 12:32:40PM -0400, Ghost Squad 57 wrote:
> Personally, I just want cgit to show the key used to sign the commit, not
> necessarily validate it. Validation could always be done on the user's side.

I would be very concerned about giving a false sense of security by
doing this.  It sounds like you want something like "good signature by
untrusted key ...", but then doing validation on the user's side
requires cloning the repository, doesn't it?

Or do you mean that the user should trust the server and just say "yes,
that's the key I expect to have signed this"?  That's not behaviour that
we should be encouraging.

> On Jul 22, 2017 8:04 AM, "John Keeping" <john at keeping.me.uk> wrote:
> 
> > On Tue, May 09, 2017 at 03:35:57AM -0400, Ghost Squad 57 wrote:
> > > Lately I've gotten into the habit of signing commits and tags with my GPG
> > > key (https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work)
> > >
> > > But it appears cgit doesn't support showing commits that have been
> > signed.
> > >
> > > Is there a way to enable this?
> >
> > No, we don't have any support for this at the moment.  What would you
> > expect to see for a signed commit?  Do you want the server to validate
> > the signature?  In which case, how should the trusted signers be
> > configured?
> >


      parent reply	other threads:[~2017-07-23 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09  7:35 No subject keithhendersonjr
2017-07-22 12:04 ` your mail john
2017-07-23 11:14   ` GPG-signing of commits was: " i
     [not found]   ` <CAGveaD7+RRwk7L-b9m3MCxokvLy7Yn6Tsw44zpOx0fDPqyYHVQ@mail.gmail.com>
2017-07-23 12:00     ` john [this message]

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=20170723120019.GK1600@john.keeping.me.uk \
    --to=cgit@lists.zx2c4.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).