Menu

S/MIME Trust Starts With the Sender, Not the Padlock
📰

S/MIME Trust Starts With the Sender, Not the Padlock

DEV Community: cybersecurity·kozhevniko·10 days ago
#k22pNgCD
Reading 0:00
15s threshold

S/MIME Trust Starts With the Sender, Not the Padlock

S/MIME can sign, verify, encrypt, and decrypt email. The visible result may be a mail client badge or a certificate icon, but the security decision happens underneath: does the certificate bind the public key to the mailbox address that the message claims, and does the client validate that identity and the certificate chain correctly?

The certificate needs an email identity

The CA/Browser Forum's S/MIME Baseline Requirements identify a publicly trusted S/MIME certificate by an extended key usage for id-kp-emailProtection and an email identity in subjectAltName , either an rfc822Name or the SMTP UTF-8 mailbox other name. The current published baseline is version 1.0.16, dated September 28, 2026.

The subject common name is not enough for a mailbox binding. A client should compare the sender address with the validated SAN identity and apply the certificate purpose.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.