Page MenuHome GnuPG

`gpg2 --list-keys --with-colons > /dev/full` exits with status 0
Open, LowPublic

Description

gpg2 --list-keys --with-colons > /dev/full exits with status 0. This makes it impossible for the caller to know if they actually received all of the output from GnuPG, or if the output was corrupted due to a transient ENOMEM or similar.

Event Timeline

DemiMarie created this object in space S1 Public.
werner added a project: Bug Report.
werner added a subscriber: werner.

The more relavant error is that there is no status output on failure which is what gpgme uses (due to double forking).

However, in real life stdout is connected to a pipe and thus won't be hit by an ENOSPC.

I note that @DemiMarie offered a patch for this over a year ago. It doesn't appear to have had any review. If it's good, maybe apply it? If it's problematic, can we identify the problem?

Done for gpg. Needs to be done for gpgsm.