Change Details

This is a re-opening of a query that was summarily closed without providing me the opportunity to respond. Below please find the original post and the response by the individual who closed the issue. I will address the items raised in the responders post here: 1. Dear ikloecker, there is not even one offensive word in my query. I do not understand why you think I was "yell at us." I can only guess that you took offense at my sentence that used ALL CAPS. I did that solely for the purpose of drawing the readers eyes to that sentence because my query was long and sometimes the major part of a request gets overlooked when it is in amongst a bunch of other text. If that is your concern, then I apologise that you took offense to capital letters. 2. My query did in fact list the version of gpg4win as 4.0.3 If there is some other designation that you require, please advise me of such and I will happily provide. 3. I am not a programmer anymore. I was decades ago. I an not a pgp / gpg expert either. I used whatever the default setting was in gpg4win / Kleopatra and the default setting in OpenKeyChain. If you can explain how I can reveal what the defaults are in each program, I will happily provide those details as well. If in addition to that I can re-install gpg4win and create test keys and create a test file and include all of them. No hesitation there either. 4. If the default for gpg4win is to use the AEAD feature that you and the Github article refer to, then yes I understand why a key created originally from gpg4win / Kleopatra would be rejected by OpenKeyChain. However, when I created keys on OpenKeyChain and then imported them to gpg4win / Kleopatra and tried to use those imported keys to then encrypt a file on gpg4win / Kleopatra and emailed it to my smartphone and tried to decrypt using OpenKeyChain, it failed. This I do not understand since the keys were originally created on OpenKeyChain. Does the importing of those keys to gpg4win / Kleopatra enable the AEAD feature by default somehow on an imported key ? 5. Can you please advise how to disable this AEAD feature in gpg4win / Kleopatra since the problem is not solved for me since I cannot use keys that are created with either program to email from Windows gpg4win / Kleopatra to OpenKeyChain. I indicated this in my query. 6. If you confidently state it is not a bug and is simply that AEAD must be disabled in gpg4win / Kleopatra to resolve. And if that is true even though imported keys that were created by OpenKeyChain still would not allow successful transmission from gpg4win / Kleopatra to OpenKeyChain, please advise me how to disable AEAD and I will happily re-test and report back my findings. Thank you for your anticipated assistance. If you encrypt a file with Windows gpg4win / Kleopatra and email it to an Android device and try to use OpenKeyChain to Decrypt you receive the following error: Unknown filename (touch to open) Encountered an error reading input data! Processing input data Attempting to process OpenPGP data Encountered an error reading input data! This problem occurs both if you create the keys on gpg4win / Kleopatra and export to OpenKeychain AND if you create the keys on OpenKeyChain and export to gpg4win. If you create keys on OpenKeyChain and export the keys to gpg4win / Kleopatra, you are able to encrypt a file on Android OpenKeychain and email to Windows device and use gpg4win / Kleopatra to decrypt. If you create keys on gpg4win / Kleopatra and export to OpenKeyChain and then try to encrypt on Android OpenKeyChain and email to Windows device gpg4win / Kleopatra, the file will not decrypt. There is something in the creation of keys on gpg4win / Kleopatra that is not working properly with OpenKeyChain. This has been reported on Github, but it was thought to be a problem with OpenKeyChain. However, based on the behavior, I believe it is a problem which is in gpg4win / Kleopatra. Here are the Github links: https://github.com/open-keychain/open-keychain/issues/2096 https://github.com/keybase/keybase-issues/issues/4025#issuecomment-874497887 PLEASE DEBUG AND PATCH GPG4WIN / KLEOPATRA AS SOON AS POSSIBLE. INTEROPERABILITY OF PGP / GPG BETWEEN WINDOWS AND ANDROID IS IMPERATIVE. Thank you. Version gpg4win 4.0.3 ikloecker closed this task as Invalid.Thu, Aug 11, 10:29 PM ikloecker added a subscriber: ikloecker. Comment Actions Please don't yell at us! If you want us to take your bug report seriously, then you really have to give us more details. Start by telling us which version of gpg4win you are using. Next tell us what kind of keys are you using? Maybe you can create test keys and add them to this bug report. And you can attach an encrypted test file to this bug report, so that we can check whether we see anything peculiar. But wait ... Reading https://github.com/open-keychain/open-keychain/issues/2096 it seems that OpenKeyChain doesn't support AEAD. gpg 2.3 (and a gpg4win using this version) will use AEAD encryption if the keys indicate that an AEAD algorithm can be used. Obviously, keys created with gpg 2.3 will indicate this. If you need interoperability with other implementations of OpenPGP that lacks features like AEAD, then you have to make sure that the keys you use do not indicate features that the other implementation of OpenPGP, e.g. OpenKeyChain, doesn't support. Incidentally, you have already found the solution: Simply create the keys with OpenKeyChain and be happy. I'm closing this issue because there is no bug in gpg. And there is no bug in OpenKeyChain either. There is simply a feature missing in OpenKeyChain which forces you to take care to use only keys that are compatible with OpenKeyChain.

This is a re-opening of a query that was summarily closed without providing me the opportunity to respond. Below please find the original post and the response by the individual who closed the issue. I will address the items raised in the responder's post here: 1. Dear ikloecker, there is not even one offensive word in my query. I do not understand why you think that I was "yell at us." I can only guess that you took offense at my sentence that used ALL CAPS. I did that solely for the purpose of drawing the readers eyes to that sentence because my query was long and sometimes the major part of a request gets overlooked when it is in amongst a bunch of other text. If that is your concern, then I apologise that you took offense to capital letters. 2. My query did in fact list the version of gpg4win as 4.0.3 If there is some other designation that you require, please advise me of such and I will happily provide. 3. I am not a programmer anymore. I was decades ago. I am not a pgp / gpg expert either. I used whatever the default settings were in gpg4win / Kleopatra and the default settings in OpenKeyChain. If you can explain how I can reveal what the defaults are in each program, I will happily provide those details as well. In addition to that I can re-install gpg4win and create test keys and create a test file and include all of them in a reply. No hesitation there either. 4. If the default for gpg4win is to use the AEAD feature that you and the Github article refer to, then yes I understand why a key created originally from gpg4win / Kleopatra would be rejected by OpenKeyChain. However, when I created keys on OpenKeyChain and then imported them to gpg4win / Kleopatra and then tried to use those imported keys to encrypt a file on gpg4win / Kleopatra and email it to my smartphone and tried to decrypt using OpenKeyChain, it failed. This I do not understand since the keys were originally created on OpenKeyChain. Does the importing of those keys to gpg4win / Kleopatra enable the AEAD feature by default somehow on an imported keys ? 5. Can you please advise how to disable this AEAD feature in gpg4win / Kleopatra since the problem is not solved for me since I cannot use keys that are created with either the Windows program nor the Android program to email from Windows gpg4win / Kleopatra to Android OpenKeyChain. I indicated this in my query. Sorry if that was unclear to you. 6. If you confidently state it is not a bug and is simply that AEAD must be disabled in gpg4win / Kleopatra to resolve my issue, and if that is true even though the imported keys that were created by OpenKeyChain and then imported to gpg4win / Kleopatra still would not allow successful transmission from gpg4win / Kleopatra to OpenKeyChain, please advise me how to disable AEAD and I will happily re-test and report back my findings. Thank you for your anticipated assistance. GPGNewbie9000 Original Post and Response: If you encrypt a file with Windows gpg4win / Kleopatra and email it to an Android device and try to use OpenKeyChain to Decrypt you receive the following error: Unknown filename (touch to open) Encountered an error reading input data! Processing input data Attempting to process OpenPGP data Encountered an error reading input data! This problem occurs both if you create the keys on gpg4win / Kleopatra and export to OpenKeychain AND if you create the keys on OpenKeyChain and export to gpg4win. If you create keys on OpenKeyChain and export the keys to gpg4win / Kleopatra, you are able to encrypt a file on Android OpenKeychain and email to Windows device and use gpg4win / Kleopatra to decrypt. If you create keys on gpg4win / Kleopatra and export to OpenKeyChain and then try to encrypt on Android OpenKeyChain and email to Windows device gpg4win / Kleopatra, the file will not decrypt. There is something in the creation of keys on gpg4win / Kleopatra that is not working properly with OpenKeyChain. This has been reported on Github, but it was thought to be a problem with OpenKeyChain. However, based on the behavior, I believe it is a problem which is in gpg4win / Kleopatra. Here are the Github links: https://github.com/open-keychain/open-keychain/issues/2096 https://github.com/keybase/keybase-issues/issues/4025#issuecomment-874497887 PLEASE DEBUG AND PATCH GPG4WIN / KLEOPATRA AS SOON AS POSSIBLE. INTEROPERABILITY OF PGP / GPG BETWEEN WINDOWS AND ANDROID IS IMPERATIVE. Thank you. Version gpg4win 4.0.3 ikloecker closed this task as Invalid.Thu, Aug 11, 10:29 PM ikloecker added a subscriber: ikloecker. Comment Actions Please don't yell at us! If you want us to take your bug report seriously, then you really have to give us more details. Start by telling us which version of gpg4win you are using. Next tell us what kind of keys are you using? Maybe you can create test keys and add them to this bug report. And you can attach an encrypted test file to this bug report, so that we can check whether we see anything peculiar. But wait ... Reading https://github.com/open-keychain/open-keychain/issues/2096 it seems that OpenKeyChain doesn't support AEAD. gpg 2.3 (and a gpg4win using this version) will use AEAD encryption if the keys indicate that an AEAD algorithm can be used. Obviously, keys created with gpg 2.3 will indicate this. If you need interoperability with other implementations of OpenPGP that lacks features like AEAD, then you have to make sure that the keys you use do not indicate features that the other implementation of OpenPGP, e.g. OpenKeyChain, doesn't support. Incidentally, you have already found the solution: Simply create the keys with OpenKeyChain and be happy. I'm closing this issue because there is no bug in gpg. And there is no bug in OpenKeyChain either. There is simply a feature missing in OpenKeyChain which forces you to take care to use only keys that are compatible with OpenKeyChain.

This is a re-opening of a query that was summarily closed without providing me the opportunity to respond. Below please find the original post and the response by the individual who closed the issue. I will address the items raised in the responder's post here: 1. Dear ikloecker, there is not even one offensive word in my query. I do not understand why you think that I was "yell at us." I can only guess that you took offense at my sentence that used ALL CAPS. I did that solely for the purpose of drawing the readers eyes to that sentence because my query was long and sometimes the major part of a request gets overlooked when it is in amongst a bunch of other text. If that is your concern, then I apologise that you took offense to capital letters. 2. My query did in fact list the version of gpg4win as 4.0.3 If there is some other designation that you require, please advise me of such and I will happily provide. 3. I am not a programmer anymore. I was decades ago. I anI am not a pgp / gpg expert either. I used whatever the default setting wass were in gpg4win / Kleopatra and the default settings in OpenKeyChain. If you can explain how I can reveal what the defaults are in each program, I will happily provide those details as well. If in addition to that I can re-install gpg4win and create test keys and create a test file and include all of them in a reply. No hesitation there either. 4. If the default for gpg4win is to use the AEAD feature that you and the Github article refer to, then yes I understand why a key created originally from gpg4win / Kleopatra would be rejected by OpenKeyChain. However, when I created keys on OpenKeyChain and then imported them to gpg4win / Kleopatra and then tried to use those imported keys to then encrypt a file on gpg4win / Kleopatra and emailed it to my smartphone and tried to decrypt using OpenKeyChain, it failed. This I do not understand since the keys were originally created on OpenKeyChain. Does the importing of those keys to gpg4win / Kleopatra enable the AEAD feature by default somehow on an imported keys ? 5. Can you please advise how to disable this AEAD feature in gpg4win / Kleopatra since the problem is not solved for me since I cannot use keys that are created with either the Windows program nor the Android program to email from Windows gpg4win / Kleopatra to Android OpenKeyChainain. I indicated this in my query. I indicated this in my querySorry if that was unclear to you. 6. If you confidently state it is not a bug and is simply that AEAD must be disabled in gpg4win / Kleopatra to resolve. my issue, Andand if that is true even though the imported keys that were created by OpenKeyChain and then imported to gpg4win / Kleopatra still would not allow successful transmission from gpg4win / Kleopatra to OpenKeyChain, please advise me how to disable AEAD and I will happily re-test and report back my findings. Thank you for your anticipated assistance. GPGNewbie9000 Original Post and Response: If you encrypt a file with Windows gpg4win / Kleopatra and email it to an Android device and try to use OpenKeyChain to Decrypt you receive the following error: Unknown filename (touch to open) Encountered an error reading input data! Processing input data Attempting to process OpenPGP data Encountered an error reading input data! This problem occurs both if you create the keys on gpg4win / Kleopatra and export to OpenKeychain AND if you create the keys on OpenKeyChain and export to gpg4win. If you create keys on OpenKeyChain and export the keys to gpg4win / Kleopatra, you are able to encrypt a file on Android OpenKeychain and email to Windows device and use gpg4win / Kleopatra to decrypt. If you create keys on gpg4win / Kleopatra and export to OpenKeyChain and then try to encrypt on Android OpenKeyChain and email to Windows device gpg4win / Kleopatra, the file will not decrypt. There is something in the creation of keys on gpg4win / Kleopatra that is not working properly with OpenKeyChain. This has been reported on Github, but it was thought to be a problem with OpenKeyChain. However, based on the behavior, I believe it is a problem which is in gpg4win / Kleopatra. Here are the Github links: https://github.com/open-keychain/open-keychain/issues/2096 https://github.com/keybase/keybase-issues/issues/4025#issuecomment-874497887 PLEASE DEBUG AND PATCH GPG4WIN / KLEOPATRA AS SOON AS POSSIBLE. INTEROPERABILITY OF PGP / GPG BETWEEN WINDOWS AND ANDROID IS IMPERATIVE. Thank you. Version gpg4win 4.0.3 ikloecker closed this task as Invalid.Thu, Aug 11, 10:29 PM ikloecker added a subscriber: ikloecker. Comment Actions Please don't yell at us! If you want us to take your bug report seriously, then you really have to give us more details. Start by telling us which version of gpg4win you are using. Next tell us what kind of keys are you using? Maybe you can create test keys and add them to this bug report. And you can attach an encrypted test file to this bug report, so that we can check whether we see anything peculiar. But wait ... Reading https://github.com/open-keychain/open-keychain/issues/2096 it seems that OpenKeyChain doesn't support AEAD. gpg 2.3 (and a gpg4win using this version) will use AEAD encryption if the keys indicate that an AEAD algorithm can be used. Obviously, keys created with gpg 2.3 will indicate this. If you need interoperability with other implementations of OpenPGP that lacks features like AEAD, then you have to make sure that the keys you use do not indicate features that the other implementation of OpenPGP, e.g. OpenKeyChain, doesn't support. Incidentally, you have already found the solution: Simply create the keys with OpenKeyChain and be happy. I'm closing this issue because there is no bug in gpg. And there is no bug in OpenKeyChain either. There is simply a feature missing in OpenKeyChain which forces you to take care to use only keys that are compatible with OpenKeyChain.