Smime signing broken in NC 28?

gvs77 · December 21, 2023, 12:50pm

I upgrade to Nextcloud 28 and the new mailapp. After that signing mails with Smime gives problems. The message is signed with the correct key but when validating it, the signature is always invalid. The same cert works on Thunderbird and Android perfectly.

Anyone having this? I’m also missing an option to auto-sign all mails, but as long as it is broken, that doesn’t help

tflidd · December 23, 2023, 6:10pm

There is a bug report, please continue discussion on solving it on the bug tracker:

github.com/nextcloud/mail

Nextcloud mail 3.5.0 generates invalid smime signature

opened 12:57PM - 21 Dec 23 UTC

gvansanden

bug 0. to triage regression

### Steps to reproduce 1. Set up a mailaccount and add a certificate 2. Send a… mail (to self) and smime sign it 3. Look at the mail in the app AND external apps like Thunderbird ### Expected behavior The signature should be valid ### Actual behavior The mail is signed with the correct key/cert but the signature is invalid ### Mail app version 3.5.0 ### Mailserver or service Dovecot ### Operating system Ubuntu 22.04 ### PHP engine version PHP 8.1 ### Web server Apache (supported) ### Database PostgreSQL ### Additional info _No response_

gvs77 · December 23, 2023, 8:25pm

Yes, I filed it sometime after this post when I concluded it really was
a bug.
Seems confirmed by now as well

3EE45A47 · February 16, 2024, 10:15am

somehow I think, this could be related?:

tflidd · February 16, 2024, 2:48pm

I don’t know the details about why the verification process fails. By default, they probably either trust the system CAs or a CA list within Nextcloud. Usually, there are a few responses to the mail app questions, if you can’t wait, check the bug tracker and the repo, if you find information.