Please enable JavaScript.

Coggle requires JavaScript to display documents.

Kryptographie (Verfahren (Asymmetrisch (Asymmetrisches Schlüsselpaar…

- - - - RC4
      - Blowfish
      - Twofish
      - DES
      - 3DES
      - AES
  - - - Geheimer privater Schlüssel
      - Freier öffentlicher Schlüssel
    - - Diffie-Hellman
      - RSA
- - - - RFC 2246
      - to provide privacy and data integrity between two communicating applications
      - The TLS protocol ensures this by encrypting data so that any third party is unable to intercept the communication
      - TLS protocol protects the integrity of the message and ensures it is not being tampered
      - Authenticity (Not clear who you are talking with): Authenticity is used to make sure that you really communicate with the partner you want to. To achieve these different kinds of techniques can be used, e.g. Pre-shared keys that are configured on both sites, Elliptic Curves or RSA as public/private key algorithms. It ensures that the parties exchanging information are who they claim to be. The server side of the channel is always authenticated; the client side is optionally authenticated.
        
        Integrity (Someone might alter content): Integrity is used to make sure that nobody in between site A and B (for example) changed some parts of the shared information i.e. Data sent over the channel after establishment cannot be modified by attackers without detection. Therefore a hash is calculated and added to a packet. This can be achieved by using hashing algorithms like MD5, SHA (1,2) and so on. To really make sure that no one is even able to modify the hash HMACs are used.
        
        Confidentiality (Anyone can see content): Confidentiality is used to make sure that nobody in between site A and B is able to read what data or information is sent between the two sites. TLS uses a combination of symmetric and asymmetric encryption to ensure message privacy. During the TLS handshake, the TLS client and server agree an encryption algorithm and a shared secret key to be used for one session only. All messages transmitted between the TLS client and server are encrypted using that algorithm and key, ensuring that the message remains private even if it is intercepted. Because TLS uses asymmetric encryption when transporting the shared secret key, there is no key distribution problem.