Using GpgOL from Gpg4win 3.0.0:
An S/MIME encrypted email that has been successfully send, cannot be opened in the send folder.
Originally this report was broader and about:
Several Users report, that they can't decrypt mails that are encrypted and signed via GpgOL, or that encrypted and signed files via GpgEX are corrupt.
This may also cause issue in T3441.
- Broken Mails - [[ https://wald.intevation.org/forum/forum.php?thread_id=1774&forum_id=21&group_id=11 | 1 ]]
- Broken Files - [[http://lists.wald.intevation.org/pipermail/gpg4win-users-de/2017-October/000946.html | 1]] [[https://wald.intevation.org/forum/forum.php?thread_id=1782&forum_id=21&group_id=11| 2]]
The Logs we received until now to analyze the issue further:
>>! In T3441#103991, @JochenSaalfeld wrote:
> I recieved the Log File of a user which may helps analyzing this problem further {F193654}
>>! In T3441#104003, @JochenSaalfeld wrote:
> This doesn't seem just to affect E-Mails but also File-Encryption.
>
> We had [[ https://wald.intevation.org/forum/forum.php?thread_id=1774&forum_id=21&group_id=11 | several ]] reports in the last couple of days about [[ http://lists.wald.intevation.org/pipermail/gpg4win-users-de/2017-October/000946.html |Problems]] with file encryption. However, the Person who sent me the log about this issue with Mails, had also issues with encrypting Files via S/MIME.
>
>
>
>
>
>> Signieren => ok
>>
>> Verschlüsseln, egal ob nur an sich selbst oder zusätzlich an einen Fremden
>> => ok
>>
>> Signieren + Verschlüsseln => Resultierende Datei ist viel zu klein, ca 3 Kb,
>> scheint nur der Verschlüsselungsheader enthalten, nicht aber die eigentliche
>> Datei. Beim Entschlüssen und Prüfen wird eine leere Datei (0 Byte) mit
>> korrektem Namen angelegt, die wohl eigentlich die ehemals zu
>> verschlüsselnden Daten enthalten sollte.
>>
>> Weiterhin ist aufgefallen:
>> Importiert man einen eigenen SMime-Schlüssel (pub/sec), ist die Ausgabe von
>> gpgsm -K ok.
>>
>> Importiert man danach zusätzlich nur einen fremden Pub-Key, tauchen bei der
>> Ausgabe von gpgsm -K Meldungen mit
>> gpgsm: DBG: chan_0x000000d8 <- ERR 67108881 Kein geheimer Schl³ssel <GPG Age
>> auf!?
>>
>> **********************
>> Microsoft Windows [Version 6.1.7601]
>> Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
>>
>> C:\Users\CLEANED>gpgsm -K
>> gpgsm: enabled debug flags: x509 mpi crypto memory cache memstat hashing ipc
>> gpgsm: DBG: get_keygrip for public key
>> gpgsm: DBG: keygrip= CF CA 58 44 82 22 EC AA F7 7E EF 8C C4 5F 0D 6D B4 E4 1
>>
>> gpgsm: DBG: chan_0x000000d8 <- OK Pleased to meet you
>> gpgsm: DBG: connection to agent established
>> gpgsm: DBG: chan_0x000000d8 -> RESET
>> gpgsm: DBG: chan_0x000000d8 <- OK
>> gpgsm: DBG: chan_0x000000d8 -> GETINFO version
>> gpgsm: DBG: chan_0x000000d8 <- D 2.2.1
>> gpgsm: DBG: chan_0x000000d8 <- OK
>> gpgsm: DBG: chan_0x000000d8 -> OPTION allow-pinentry-notify
>> gpgsm: DBG: chan_0x000000d8 <- OK
>> gpgsm: DBG: chan_0x000000d8 -> HAVEKEY CFCA58448222ECAAF77EEF8CC45F0D6DB4E41
>> gpgsm: DBG: chan_0x000000d8 <- ERR 67108881 Kein geheimer Schl³ssel <GPG Age
>> gpgsm: DBG: get_keygrip for public key
>> gpgsm: DBG: keygrip= 02 07 A2 0D 02 EF 3B C6 8F F8 5A CF 46 6C 51 04 69 D8 F
>>
>> gpgsm: DBG: chan_0x000000d8 -> HAVEKEY 0207A20D02EF3BC68FF85ACF466C510469D8F
>> gpgsm: DBG: chan_0x000000d8 <- ERR 67108881 Kein geheimer Schl³ssel <GPG Age
>> gpgsm: DBG: get_keygrip for public key
>> gpgsm: DBG: keygrip= 07 58 5C 31 C9 A6 F4 F7 F3 38 6C 7B 2E ED 06 F2 70 94 D
>>
>> gpgsm: DBG: chan_0x000000d8 -> HAVEKEY 07585C31C9A6F4F7F3386C7B2EED06F27094D
>> gpgsm: DBG: chan_0x000000d8 <- OK