I found the answer I was looking for by enabling status-fd
[GNUPG:] BEGIN_DECRYPTION
[GNUPG:] PLAINTEXT 62 167772160 small.doc
[GNUPG:] PLAINTEXT_LENGTH 19456
[GNUPG:] DECRYPTION_OKAY
Wes
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http
le name guaranteed to be just a file name, or could
it be a full path, which would present a rather significant problem?
Wes
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
ed message, nor in a
hex dump of the PGP data, to indicate the original file name.
I don't see any way in GPG to read the original file name, or to write the
output to a file of the original name (or conversely to set the file name).
Is this possible? I
a
hex dump of the PGP data, to indicate the original file name.
I don't see any way in GPG to read the original file name, or to write the
output to a file of the original name (or conversely to set the file name).
Is this possible? I'm u
ns basedn=whatever-you-like
I didn't see that in the keyserver options. I'll try it out.
Thanks
Wes
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
relying on the cn=PGPServerInfo
entry.
Am I overlooking something? Is this possible today? If not, and we
developed the code, would be it something that could be integrated into GPG
for others to use?
Wes
___
Gnupg-users mailing list
Gnupg-users