230 likes | 382 Views
Internet Security 1 ( IntSi1 ). 7 Secure Email. Prof. Dr. Andreas Steffen Institute for Internet Technologies and Applications (ITA). Communication layers. Security protocols. Application layer. ssh , S/MIME, PGP, Kerberos , WSS. Transport layer. SSL, TLS. Network layer. IPsec.
E N D
Internet Security 1 (IntSi1) 7 Secure Email Prof. Dr. Andreas SteffenInstitute for Internet Technologies and Applications (ITA)
Communication layers Security protocols Application layer ssh, S/MIME, PGP, Kerberos, WSS Transport layer SSL, TLS Network layer IPsec Data Link layer [PPTP, L2TP], IEEE 802.1X,IEEE 802.1AE, IEEE 802.11i (WPA2) Physical layer Quantum Cryptography Security Protocols for the OSI Stack
Internet Security 1 (IntSi1) 7.1 S/MIME
From: trinity@matrix.orgTo: neo@matrix.orgMIME–Version: 1.0Content–Type: multipart/mixed;boundary=boundary1 --boundary1 Content–Type: text/plain; charset=us-asciiDear Neo, please study the attached Word document.--boundary1 Content–Type: application/msword; name="Matrix.doc"Content–Transfer–Encoding: base64ghyHhHUujhJhjH77n8HHGTrfvbnj756tbB9HG4VQpfyF467GhIGfH 4VQpfyF467GhIGfHfYT6jH77n8HHGghyHhHUujhJh756tbTrfv=--boundary1-- MIME – Multipurpose Internet Mail ExtensionRFC 1521 / RFC 1522
Content–Type: multipart/signed; protocol="application/pkcs7–signature"; micalg=sha1; boundary=boundary1 --boundary1 Content–Type: text/plainThis is a clear-signed message.--boundary1 MIME entity to be signed Content–Type: application/pkcs7–signature; name=smime.p7sContent–Transfer-Encoding: base64Content–Disposition: attachment; filename=smime.p7s ghyHhHUujhJhjH77n8HHGTrfvbnj756tbB9HG4VQpfyF467GhIGfH 4VQpfyF467GhIGfHfYT6jH77n8HHGghyHhHUujhJh756tbTrfv=--boundary1-- S/MIME – Signed Message Format IRFC 1847 / RFC 2311 / PKCS #7
Content–Type: multipart/signed; protocol="application/pkcs7–signature"; micalg=sha1; boundary=boundary1 --boundary1 Content–Type: multipart/mixed; boundary=boundary2 ... multipart message with various MIME-types ...--boundary1 Content–Type: application/pkcs7–signature; name=smime.p7sContent–Transfer-Encoding: base64Content–Disposition: attachment; filename=smime.p7s ghyHhHUujhJhjH77n8HHGTrfvbnj756tbB9HG4VQpfyF467GhIGfH 4VQpfyF467GhIGfHfYT6jH77n8HHGghyHhHUujhJh756tbTrfv=--boundary1-- S/MIME – Signed Message comprisingMultiple Attachments
versiondigestAlgorithmscontentInfocertificates (OPTIONAL)crls (OPTIONAL)signerInfos (SET OF) empty field (content carried inseparate MIME entity) several signers possible versionissuerAndSerialNumberdigestAlgorithmauthenticatedAttributesdigestEncryptionAlgorithmencryptedDigestunauthenticatedAttributes signature PKCS #7 – Public Key Cryptography StandardCryptographic Message Syntax Standard • ASN.1 structure for the SignedData content type • ASN.1 structure for the SignerInfo type
DigestAlgorithm#1 DigestAlgorithm#2 DigestAlgorithm#n Private Key#1 Private Key#2 Private Key#n Signature#1 Signature #2 Signature#n Signed Message with Multiple Signatures MIME Entity (single-part or multi-part)
Content–Type: application/pkcs7–mime; smime–type=signed–data; name=smime.p7mContent–Transfer-Encoding: base64Content–Disposition: attachment; filename=smime.p7m ghyHhHUujhJhjH77n8HHGTrfvbnj756tbB9HG4VQpfyF467GhIGfH 4VQpfyF467GhIGfHfYT6jH77n8HHGghyHhHUujhJh756tbTrfv= S/MIME – Signed Message Format IIRFC 2311 / PKCS #7 • MIME contentcarriedwithin PKCS#7 Signed Data Object • This alternative signingformatisoptionallyusedby MS Outlook • Pro: MIME contentis not pronetochangesofthetransferencodingenforcedby intermediate mailtransferagents. • Contra: In order toreadtheemedded MIME message, thereceiver‘smailclient must support S/MIME.
Content–Type: application/pkcs7–mime; smime–type=enveloped–data; name=smime.p7mContent–Transfer-Encoding: base64Content–Disposition: attachment; filename=smime.p7m ghyHhHUujhJhjH77n8HHGTrfvbnj756tbB9HG4VQpfyF467GhIGfH 4VQpfyF467GhIGfHfYT6jH77n8HHGghyHhHUujhJh756tbTrfv= several recipients possible(encrypted symmetric key) versionrecipientInfosencryptedContentInfo contentTypecontentEncryptionAlgorithmencryptedContent encrypted MIME entity(single-part or multi-part) S/MIME – Encrypted Message FormatRFC 2311 / PKCS #7 • ASN.1 structure for the EnvelopedData content type
RandomKey Symmetric Encryption Algorithm Encrypted MIME Entity Public Key#1 Public Key#2 Public Key#n EncryptedKey #1 EncryptedKey #2 EncryptedKey #n Encrypted Message with Multiple RecipientsEnvelope using Symmetric Encryption MIME Entity (single-part or multi-part)
Content–Type: application/pkcs7–mime; smime–type=signed–data; ... signedData SignedData ::= { ... contentInfo} MIME entity to be signed MIME entity to be encrypted Content–Type: application/pkcs7–mime; smime–type=enveloped–data; ... envelopedData EnvelopedData ::= { ... encryptedContentInfo} encrypted MIME entity S/MIME – Signed and Encrypted Messages ISigning before Encryption • Signature(s) not visible before decryption (Anonymity)
Content–Type: application/pkcs7–mime; smime–type=signed–data; ... signedData SignedData ::= { ... contentInfo} MIME entity to be signed Content–Type: application/pkcs7–mime; smime–type=enveloped–data; ... envelopedData EnvelopedData ::= { ... encryptedContentInfo} MIME entity to be signed encrypted MIME entity S/MIME – Signed and Encrypted Messages IIEncryption before Signing • Signature(s) can be checked before decryption (Trust)
S/MIME – Certificates (ownandotherpeople‘s)MozillaThunderbird
Antje Bob Antje Kool CA #3 #2 #2 #0 Kool CA Kool CA Kool CA Kool CA S/MIME Summary • Sign Antje Bodo Signwithprivate key Verifywithpublickey Verifywithpublickey • Encrypt Dear Bodo,… Dear Antje,… Antje Bodo Antje Bodo Decryptwithprivate key Encryptwithpublickey