Please enable JavaScript.

Coggle requires JavaScript to display documents.

PROTOCOLS (S/MIME (S/MIME Message Content Types (SignedData (signedData…

- - - - signedData Steps
        
        Encrypt the message digest with the signer’s private key
        
        Prepare a block known as SignerInfo that contains
        
        signer’s public-key certificate,
        
        identifier of the message digest algorithm
        
        identifier of the algorithm used to encrypt the message digest
        
        the encrypted message digest
        
        Compute the message digest to be signed
        
        Select a message digest algorithm (SHA or MD5)
    - - envelopedData Steps
        
        For each recipient, encrypt the session key with the recipient’s public RSA key
        
        For each recipient, prepare a block known as RecipientInfo that contains:
        
        identifier of the recipient’s public-key certificate
        
        identifier of the algorithm used to encrypt the session key
        
        encrypted session key
        
        Generate a session key for a particular symmetric encryption algorithm
        
        Encrypt the message content with the session key
- - - - Content-ID
        
        Used to identify MIME entities uniquely in multiple contexts
      - Content-Transfer-Encoding
        
        Indicates the type of transformation that has been used to represent the body of the message in a way that is acceptable for mail transport
      - Content-Description
        
        A text description of the object with the body; this is useful when the object is not readable
      - Content-Type
        
        Describes the body with detail that the receiving MUA can pick an appropriate agent or mechanism to represent the data otherwise deal with data in an appropriate manner
      - MIME-Version
        
        Must have the parameter value 1.0
        
        This field indicates that the message conforms to RFCs 2045 and 2046