From: Christopher Bertels <mailinglist@flasht.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] fix GPG "hang" on malformed PGP message (detached signature)
Date: Fri, 08 Oct 2010 16:36:04 +0200 [thread overview]
Message-ID: <1286548547-sup-3965@bakkdoor-thinkpad> (raw)
In-Reply-To: <1286541818-sup-2877@mithink>
Excerpts from Michael Hamann's message of Fr Okt 08 14:53:56 +0200 2010:
> Hi,
>
> Excerpts from Sascha Silbe's message of 2010-10-05 13:25:33 +0200:
> > - message = run_gpg "--output #{output_fn.path} --skip-verify --yes --decrypt #{payload_fn.path}", :interactive => true
> > + message = run_gpg "--output #{output_fn.path} --multifile --skip-verify --yes --decrypt #{payload_fn.path}", :interactive => true
>
> This change breaks GPG decryption completely for me, not a single
> message I've tried is decrypted anymore. The error message I'm getting
> is Error while running gpg: gpg: --output doesn't work for this command.
> I'm using gpg version 1.4.10. The complete gpg command that is executed
> is:
Yup, same for me :(
>
> LC_MESSAGES=C /usr/bin/gpg --quiet --batch --no-verbose --logger-fd 1 --use-agent --output /tmp/redwood.output20101008-5410-lj1dh3 --multifile --skip-verify --yes --decrypt /tmp/redwood.payload20101008-5410-1qtud0x > /tmp/redwood.output20101008-5410-2rsbb5 2> /dev/null
>
> Michael
--
================================
Christopher Bertels
http://www.fancy-lang.org
http://www.adztec-independent.de
GPG Key ID: 0x2345b203
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-10-08 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 11:25 Sascha Silbe
2010-10-08 4:20 ` Rich Lane
2010-10-08 12:53 ` Michael Hamann
2010-10-08 14:36 ` Christopher Bertels [this message]
2010-10-08 20:09 ` Rich Lane
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=1286548547-sup-3965@bakkdoor-thinkpad \
--to=mailinglist@flasht.de \
--cc=sup-devel@rubyforge.org \
/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