liveBook · Manning

S/MIME

As explained in Real-World Cryptography

S/MIME is a standard for securing email with encryption and digital signatures based on public-key cryptography.

When a company needs employees to exchange confidential email, S/MIME uses public-key infrastructure to bind identities to public keys. It extends MIME and normally runs over SMTP, securing the message body with encryption and digital signatures. section 10.3.3

S/MIME’s practical shape is defined by three choices:

  • Trust comes from a public key infrastructure rather than PGP’s web-of-trust model, making organizational identity management a natural fit. section 10.3.3 section 10.6
  • Email integration is incomplete: the body may be encrypted, while the subject and other headers remain exposed. section 10.3.3
  • Treat it cautiously: outdated cryptography, absent authenticated encryption, imperfect clients, and exfiltration attacks weaken its security. section 10.3.3 section 10.6

A company email ecosystem

A company can use employee onboarding and offboarding processes to establish and revoke trusted identities and public keys for internal email, though modern messaging applications may provide a better alternative. section 10.3.3 section 10.6

How Real-World Cryptography covers it

How deep it goes
Explains the trust model and major integration failures, but stops short of configuration or implementation procedures.
Examples
Uses corporate employee onboarding and offboarding as the main example for establishing organizational trust.
What you can do after
Evaluate S/MIME’s organizational fit and limitations before relying on it for encrypted email.
How it connects
Connects S/MIME to public-key infrastructure, PGP, MIME, SMTP, end-to-end encryption, and email-client security.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Real-World Cryptography. The section links point to the parts of the book it draws on.