linux-kernel - Re: [RFC][PATCH v2][QUILT] Add gpg signing to quilt mail

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1317752148.18063.16.camel@gandalf.stny.rr.com>
Date:	Tue, 04 Oct 2011 14:15:46 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Greg KH <gregkh@...e.de>
Cc:	quilt-dev <quilt-dev@...gnu.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Andrew Morton <akpm@...ux-foundation.org>,
	John Kacur <jkacur@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [RFC][PATCH v2][QUILT] Add gpg signing to quilt mail

On Tue, 2011-10-04 at 11:02 -0700, Greg KH wrote:
> On Tue, Oct 04, 2011 at 01:46:34PM -0400, Steven Rostedt wrote:
> > +my $pgp = `gpg --simple-sk-checksum -a --detach-sign $pass --output - < $tmpfile`;
> 
> Try not to use gpg when calling from scripts, use gpgv instead, it
> handles things much better, and sets the return value correctly so you
> can check it (which I don't think you do here.)

You're right, I don't check the return value. I haven't figured out a
good way to pass that back to the script. Hmm, an error in the pipe
would kill the pipe.

> 
> Now if only someone can get quilt working properly for git's "split"
>  subject: lines, I would be very happy...

What issues do you have? I use quilt to send git patches all the time.

What are git's "split" subject: lines?

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/