Difference between revisions of "Secure Multipurpose Internet Mail Extensions"
(Created page with "Secure/Multipurpose Internet Mail Extensions (or S/MIME) is a protocol for sending messages that are encrypted and digitally signed. S/MIME provides for cryptographic securi...") |
|||
| Line 1: | Line 1: | ||
| − | Secure/Multipurpose Internet Mail Extensions (or S/MIME) is a protocol for sending messages that are encrypted and digitally signed. S/MIME provides for cryptographic security services such as authentication, message integrity, and non-repudiation of origin (using digital signatures). | + | Secure/Multipurpose Internet Mail Extensions (or S/MIME) is a protocol for sending messages that are encrypted and digitally signed. S/MIME provides for cryptographic security services such as authentication, message integrity, and non-repudiation of origin (using digital signatures). The first version of S/MIME was developed in 1995 by a number of security vendors. It was one of several specifications for message security. Other distinct security applications included [[Pretty Good Privacy]]. Over the following five years, S/MIME was adopted as the standard for message security. S/MIME requires the use of a dedicated email client, and the installation of a security key, or certificate from a Certificate Authority (CA). |
| − | + | S/MIME does have several practical limitations. It is not optimized for web-based mail applications. Third-parties cannot scan the encrypted messages for malware, this requires analysis of the decrypted file. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 03:29, 18 November 2015
Secure/Multipurpose Internet Mail Extensions (or S/MIME) is a protocol for sending messages that are encrypted and digitally signed. S/MIME provides for cryptographic security services such as authentication, message integrity, and non-repudiation of origin (using digital signatures). The first version of S/MIME was developed in 1995 by a number of security vendors. It was one of several specifications for message security. Other distinct security applications included Pretty Good Privacy. Over the following five years, S/MIME was adopted as the standard for message security. S/MIME requires the use of a dedicated email client, and the installation of a security key, or certificate from a Certificate Authority (CA).
S/MIME does have several practical limitations. It is not optimized for web-based mail applications. Third-parties cannot scan the encrypted messages for malware, this requires analysis of the decrypted file.
