Page MenuHome GnuPG

Issues en/decrypting data from/to a pipe.
Closed, ResolvedPublic

Description

Release: gpg 1.2.4

Environment

any

Description

It is currently difficult to de/encrypt data through a pipe. Check procedures like 'encode_crypt', 'handle_progress', and 'is_file_compressed', 'handle_plaintext' for opening the fd twice, scanning the fd, etc. These should accurately detect which I/O is on a pipe, or give the user a way to specify that which supplied file descriptors are pipes, and then require the use of options like --set-filesize, --compress-level to supply any values which the code currently attempts to extract in ways that are incompatible with pipes. Handle_plaintext should obey --enable-special-filenames. There are probably similar, issues in the reverse if stdin or stdout happens to be a file instead of a pipe.

Fix

1.3.91 will check for special filenames and handle them the same way as stdin/stout.

Release Note

Fixed in CVS

Event Timeline

Sorry, I can't see your problem. Data is piped through gpg sicense the very beginning without any problems. Whty do you want to use --set-fielseize et al? These are very special options not in general useful.