Forum: help-en
![](https://wald.intevation.org/themes/funky-wald/images/ic/mail16w.png)
![Start New Thread](https://wald.intevation.org/themes/funky-wald/images/ic/write16w.png)
RE: Cannot verify this signed file [ Reply ] By: Jochen Saalfeld on 2017-10-09 12:50 | [forum:5252] |
Since we received several similar requests to yours, I opened a bug-report: https://dev.gnupg.org/T3442 We will keep that updated! Best wishes, Jochen |
RE: Cannot verify this signed file [ Reply ] By: Dan Passegua on 2017-10-09 11:08 | [forum:5251] |
Yes, I did restart the PC. No log file written or found on my PC. |
RE: Cannot verify this signed file [ Reply ] By: Jochen Saalfeld on 2017-10-09 10:23 | [forum:5250] |
Hey, Have you restarted your PC (or all of the Gpg4win Components) afterwards? Best wishes, Jochen |
RE: Cannot verify this signed file [ Reply ] By: Dan Passegua on 2017-10-09 09:46 | [forum:5249]![]() |
I set up the log recording but nothing is being written! Please look attachment. |
RE: Cannot verify this signed file [ Reply ] By: Jochen Saalfeld on 2017-10-09 09:18 | [forum:5246] |
Hey Dan, Can you please activate your local logging (explained in the gpg4win compendium[1] in chapter 23.4). These logs help us to understand what Kleopatra tries to do and if there are any issues with the current workflow in Kleopatra itself or if there is an error with the configuration. Please feel free to clean up the log files before uploading them. Best wishes, Jochen [1] - https://files.gpg4win.org/doc/gpg4win-compendium-en.pdf |
RE: Cannot verify this signed file [ Reply ] By: Dan Passegua on 2017-10-09 09:12 | [forum:5244]![]() |
Well I try to sign a simple txt file. I am using Kleopatra 3.0.0 on windows 10 I get this result when I try to encrypt and sign: * Data signing succeeded Yes * Data available Yes * (data hash algorithm: SHA256) * Signer 1 Okay * (attr hash algorithm: SHA256) * (#133363/1.2.840.113549.1.9.1=#737570706F7274406361636572742E6F7267,CN=CA Cert Signing Authority,OU=http://www.cacert.org,O=Root CA) * (/1.2.840.113549.1.9.1=#64616E69656C654073696E617073692E6F7267,1.2.840.113549.1.9.1=#64616E69656C652E70617373616C616371756140676D61696C2E636F6D,CN=CAcert WoT User) * (/<xxxx@gmail.com>) * (/<daniele@xxxxx.org>) But If I try to decrypt and verify: * Data decryption succeeded Yes * Data available No * Encryption algorithm supported No * Number of recipients 0 And I save the result will be an empy file (0 byte)! Please look at the screen shot. Thanks |
RE: Cannot verify this signed file [ Reply ] By: Jochen Saalfeld on 2017-10-09 07:35 | [forum:5231] |
Hi Dan, Can you describe what you are trying to archive? Can you tell us more about your setup and Computer and the installed Version of Gpg4win? I downloaded you file and see that the signature is invalid but without more information I can only guess what is wrong with the file. Best wishes, Jochen |
RE: Cannot verify this signed file [ Reply ] By: Dan Passegua on 2017-10-08 09:11 | [forum:5230]![]() |
Forgot to attach signed file |
Cannot verify this signed file [ Reply ] By: Dan Passegua on 2017-10-08 09:07 | [forum:5229]![]() |
Please help me in understanding how verify this file signed by me using Kleopatra and Cacert X.509 certificate. When I sign then Kleopatra tells me that all is OK: * Data signing succeeded Yes * Data available Yes * (data hash algorithm: SHA256) * Signer 1 Okay * (attr hash algorithm: SHA256) * (#133363/1.2.840.113549.1.9.1=#737570706F7274406361636572742E6F7267,CN=CA Cert Signing Authority,OU=http://www.cacert.org,O=Root CA) * (/1.2.840.113549.1.9.1=#64616E69656C654073696E617073692E6F7267,1.2.840.113549.1.9.1=#64616E69656C652E70617373616C616371756140676D61696C2E636F6D,CN=CAcert WoT User) * (/<xxxx@gmail.com>) * (/<xxxxx@xxxxx.org>) But whenever I use Kleopatra to verify it then I get this: * Data decryption succeeded Yes * Data available No * Encryption algorithm supported No * Number of recipients 0 AND: Note: You can not be sure who encrypted this message because it is not signed. and if I try to save the result I get a 0 byte (empty) file! Thanks. |