S/MIME specifies the MIME type application/pkcs7-mime (smime-type "enveloped-data") for data enveloping (encrypting) where the whole (prepared) MIME entity to be enveloped is encrypted and packed into an object which subsequently is inserted into an application/pkcs7-mime MIME entity.īefore S/MIME can be used in any of the above applications, one must obtain and install an individual key/certificate either from one's in-house certificate authority (CA) or from a public CA. Non-repudiation of origin (using digital signatures).S/MIME provides the following cryptographic security services for electronic messaging applications:
Since it is built on CMS, MIME can also hold an advanced digital signature. S/MIME functionality is built into the majority of modern email software and interoperates between them. Change control to S/MIME has since been vested in the IETF, and the specification is now layered on Cryptographic Message Syntax (CMS), an IETF specification that is identical in most respects with PKCS #7. It was originally developed by RSA Data Security, and the original specification used the IETF MIME specification with the de facto industry standard PKCS #7 secure message format. S/MIME is on an IETF standards track and defined in a number of documents, most importantly RFC 3369, 3370, 38.
S/MIME ( Secure/Multipurpose Internet Mail Extensions) is a standard for public-key encryption and signing of MIME data.
0 kommentar(er)
