[Gpg4win-devel] Mime Type in Kleopatra

[Dave Scotese]

I encrypt a text file of sensitive information.  In the past, Kleopatra
asked if I wanted to encrypt it to ASCII ("ASCII-Armor" I think it was
called).  Now it has no such option, and the resulting encrypted file is
not ASCII.  When I use other software to decrypt it, the decryption works
but the mimetype of the result is "application/octet-stream" even though
the original file was a (Windows) text file.

I now know that I can create the ASCII-armor'ed file by copying the text in
the file to my clipboard and using Kleopatra's "Clipboard|Encrypt" feature,
but GPG4Win shouldn't be setting an incorrect mimetype when it encrypts a
text file.  it would be handy to use something like
OpenKeychain's CharsetVerifier
<https://github.com/open-keychain/open-keychain/blob/master/OpenKeychain/src/main/java/org/sufficientlysecure/keychain/util/CharsetVerifier.java#L32>
to guess a better mimetype than "application/octet-stream" which is
apparently what Kleopatra is using, and that prevents OpenKeychain from
providing the decrypted text from the file to the user, as text, upon
decryption.  I've already suggested to OpenKeychain that decryption results
with the  "application/octet-stream" mimetype could be tested (see previous
link) to see if "text/plain" would work, but that's a kludge rather than a
fix.

There is an image of the log of OpenKeychain's operation on my phone on
Github
<https://github.com/open-keychain/open-keychain/issues/2558#issuecomment-640290488>
which I interpret to mean that gpg4win is responsible for (incorrectly)
indicating the mimetype.

If this is not the appropriate place for this inquiry, please advise.

Thanks!
Dave Scotese.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wald.intevation.org/pipermail/gpg4win-devel/attachments/20200607/3716f228/attachment.html>