On Wed, 14 Jan 2015 17:40, patrick-mailingli...@whonix.org said:
Do you mean, for example, the signature could be valid, but the key that
signed it could be revoked and gpg would still exit 0?
Sure. It is just to complex to put it into one number. Consider the
case for multiple signatures -
Reading the manual for batch GPG key generation in GnuPG 2.1, I see
the following note:
Since GnuPG version 2.1 it is not anymore possible to specify a passphrase
for unattended key generation. The passphrase command is simply ignored and
‘%ask-passpharse’ is thus implicitly enabled.
I'm
On 14-01-2015 21:59, Joey Castillo wrote:
Now that we cannot specify a passphrase in the batch parameters, what
is the preferred method for batch key generation with a specified
passphrase?
Use GnuPG 1.4.18.
--
ir. J.C.A. Wevers
PGP/GPG public keys at
Hello Everyone,
I'm trying to help someone configure MacGPG 2.0.22. I've defined a group
with multiple keys in it. But when I try to encrypt to the group to test
things, I get the following error:
gpg: O g: can't encode a 256 bit key in a 0 bit frame
This happens after I tell the
On 1/14/15 7:09 PM, Anthony Papillion wrote:
gpg: O g: can't encode a 256 bit key in a 0 bit frame
This happens after I tell the program to accept the final key in the
group as valid. But it doesn't seem to be related to a key since I've
deleted the final key and it still give me the
I use Mac GPG2, but I’ve never had this problem.
You could try posting this to the MacGPG2 support page
which is here
http://support.gpgtools.org/
Sandeep Murthy
s.mur...@mykolab.com
On 2015-01-15 03:09, Anthony Papillion wrote:
Hello Everyone,
I'm trying to help someone configure MacGPG
I know that all processes have an exit code, what I meant was
if you invoke gpg interactively like gpg —edit-key key ID /email
and then execute a wrong subcommand or specify something incorrectly
then the gpg exit code will not reflect this unless the subcommand
launches another process.
Sandeep
On Wed, 14 Jan 2015 14:40, d...@fifthhorseman.net said:
gpg does use the return code to indicate failure of signature
verification.
But recall that success does not mean that the signature is good.
Check the status output or use gpgv.
Shalom-Salam,
Werner
--
Die Gedanken sind frei.
Werner Koch:
On Wed, 14 Jan 2015 14:40, d...@fifthhorseman.net said:
gpg does use the return code to indicate failure of signature
verification.
But recall that success does not mean that the signature is good.
Check the status output or use gpgv.
Do you mean, for example, the signature
Hi!
Is there a shell script or bash library for parsing gpg's --status-fd
output?
I mean, I could code it myself. But why duplicate effort and risk
messing up. Maybe there is some existing or even recommended or even
official library to do this?
(What I mean by parsing is: to get from lines
On 13-01-2015 21:38, Werner Koch wrote:
Well, we could also change the code
to trial verify with all key ids but that takes longer than needed and
may by itself be used as a DoS.
You don't need to test all keyID's - just those with the same key ID.
Assuming this is a rare occasion and
On Tue, 13 Jan 2015 21:33, dgouttegat...@incenp.org said:
[2] https://bugs.g10code.com/gnupg/issue1794
Right, this is a blocker for a 2.1.2 release.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
___
On Wed, 14 Jan 2015 00:54, 2014-667rhzu3dc-lists-gro...@riseup.net said:
I thought we already took care of this with
sig-notation issuer-...@notations.openpgp.fifthhorseman.net=%g [0]
But GnuPG does not know about this - it is Dkg's private thing. Further
this triples the required size for
Are there cases where gpg --verify will exit 0, even if verification failed?
Verification could fail internally within the gpg program, or externally because
the signature fie does not exist or is incorrectly named or maybe corrupt
e.g.
[srm@~]$ gpg --verify asig.sig; echo $?
gpg: can't open
In Unix terms, a program that has run successfully to completion
exits with status zero, no 'extra' semantic attached?
Dave
On 13 January 2015 at 19:03, Patrick Schleizer
patrick-mailingli...@whonix.org wrote:
In another thread...
Werner Koch
On Mon, 12 Jan 2015 19:52, patrick-
When it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/14/2015 02:40 PM, Daniel Kahn Gillmor wrote:
On Wed 2015-01-14 08:22:45 -0500, Sandeep Murthy wrote:
Exit codes in shells indicate problems relating to completion or
disruption of the child process invoked by a parent process.
..
16 matches
Mail list logo
