Cool. Maybe our definitions of scrape are what's causing the disagreement. Sorry about that! When I look at the code that calls the GPG binary, in the python

Cool. Maybe our definitions of scrape are what's causing the disagreement. Sorry about that! When I look at the code that calls the GPG binary, in the python lb at https://code.google.com/p/python-gnupg/ https://code.google.com/p/python-gnupg/ it seems to be reading/writing stdout/stdin. It doesn't appear to be using a socket connection, or any other non-typical way of accessing it. return Popen(cmd, shell=True, stdin=PIPE, stdout=PIPE, stderr=PIPE) def _read_response(self, stream, result): Internal method: reads all the stderr output from GPG, taking notice # only of lines that begin with the magic [GNUPG:] prefix. etc In trying to gpg in my apps, having a library which lets me generate a pgp key in memory, read it in to a string, write it out to a string, and sign/encrypt strings or binaries would be optimal. I don't want to have to worry about where the .gnupg home directory is being created.. I don't want any files stored. I don't want to access any keyservers, I'm doing all the key verification through other channels. Essentially, I'd like to be able to use GPG more like NaCL/Libsodium.