From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Carlos Rica <jasampler@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Make verify-tag a builtin.
Date: Mon, 23 Jul 2007 22:48:17 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707232242430.14781@racer.site> (raw)
In-Reply-To: <1b46aba20707231421k54ad2796i5c2f21cf11b4bea5@mail.gmail.com>
Hi,
On Mon, 23 Jul 2007, Carlos Rica wrote:
> 2007/7/23, Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> > On Mon, 23 Jul 2007, Carlos Rica wrote:
> > > +static int run_gpg_verify(const char *buf, unsigned long size, int
> > verbose)
> > > +{
> > > + struct child_process gpg;
> > > + const char *args_gpg[] = {"gpg", "--verify", "FILE", "-", NULL};
> > > + char *path, *eol;
> > > + size_t len;
> > > + int fd, ret;
> > > +
> > > + path = xstrdup(git_path("VTAG_TMP"));
> > > + fd = open(path, O_CREAT | O_TRUNC | O_WRONLY, 0600);
> > > + if (fd < 0)
> > > + return error("could not create temporary file '%s': %s",
> > > + path, strerror(errno));
> > > + if (write_in_full(fd, buf, size) < 0)
> > > + return error("failed writing temporary file '%s': %s",
> > > + path, strerror(errno));
> > > + close(fd);
> >
> > I just tested something like "gpg --verify - - < <filename>" and it
> > worked...
>
> I couldn't verify tags using "gpg --verify - - <file" as you
> pointed in your response.
As discussed on IRC, my test did not use a detached signature, while tags
_do_ use a detached signature.
Oh, well. I retract my suggestion. But I slightly disagree that having
to write a temporary file is good for security, as the gpg man page
suggests:
--verify [[sigfile] [signed-files]]
[...] To read the signed stuff from stdin, use - as the second
filename. For security reasons a detached signature cannot read
the signed material from stdin without denoting it in the above
way.
So we have to live, or die, with the temporary file.
Just one request: please use lock_file, to prevent multiple instances from
getting confused... Even if that cannot be 100% secure: if you write to
the file, and only then start gpg, there is still the odd chance for an
attacker. Even if you created the file with 0600 (very wise, BTW).
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-23 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 0:20 [PATCH] Make verify-tag a builtin Carlos Rica
2007-07-23 0:52 ` Johannes Schindelin
2007-07-23 21:21 ` Carlos Rica
2007-07-23 21:48 ` Johannes Schindelin [this message]
2007-07-23 22:31 ` Carlos Rica
2007-07-23 22:32 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2007-07-27 4:07 Carlos Rica
2007-07-27 7:05 ` Junio C Hamano
2007-07-27 19:51 ` Carlos Rica
2007-07-27 21:08 ` Junio C Hamano
2007-07-28 18:02 ` Carlos Rica
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=Pine.LNX.4.64.0707232242430.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jasampler@gmail.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).