bug#40397: 28.0.50; epg decrypt does not verify signed content in smime

[Sebastian Fieber <sebastian.fieber@web.de>]

[-- Attachment #1: Type: text/plain, Size: 426 bytes --]

Hey there,

I just thought this may be hard to test as one has to have a smime
certificate to properly receive an encrypted mail.

If someone can point me to the right approach how to fix this I may be
able to dive a bit deeper into the gnus code and submit a bug report.

This is what I have tried now just to get something:

If I alter mm-view-pkcs7-decrypt after the insert epg-decrypt-string to
call something like this:


[-- Attachment #2: Type: application/emacs-lisp, Size: 63 bytes --]

[-- Attachment #3: Type: text/plain, Size: 59 bytes --]


and adjust mm-view-pkcs7-get-type to handle a third case


[-- Attachment #4: Type: application/emacs-lisp, Size: 90 bytes --]

[-- Attachment #5: Type: text/plain, Size: 70 bytes --]


and also mm-copy-to-buffer to check for carriage returns like this:


[-- Attachment #6: Type: application/emacs-lisp, Size: 43 bytes --]

[-- Attachment #7: Type: text/plain, Size: 627 bytes --]

(can't send the carriage return properly so \r it is here instead of ^M)

I am able to get an article buffer that still has the base64 encoded
signed blob in it but after it the verified content.

I have no idea where gnus normalizes the line endings to just newlines
and why the mm-view-pkcs7-get-type adjustment is needed. But calling
gnus-ime-display-part is of course not the right approach here. First
there should be some check if the decrypted content needs to be parsed
and handled again but I have no idea which function to write or feed the
decrypted content to.

I hope this may be helpful

Best regards
Sebastian