Scribd
Upload
17 views10 pages

Cryptography

The document discusses the importance of TLS/SSL protocols in securing online communication through encryption, authentication, and integrity. It explains the role of digital certificates and certificate authorities (CAs) in verifying identities and managing certificates, while also addressing challenges in certificate revocation mechanisms. Additionally, it outlines the TLS handshake process and the practical implications of compromised certificates in online security.

Uploaded by

Kelvin Byabato
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
17 views10 pages

Cryptography

The document discusses the importance of TLS/SSL protocols in securing online communication through encryption, authentication, and integrity. It explains the role of digital certificates and certificate authorities (CAs) in verifying identities and managing certificates, while also addressing challenges in certificate revocation mechanisms. Additionally, it outlines the TLS handshake process and the practical implications of compromised certificates in online security.

Uploaded by

Kelvin Byabato
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Securing Online Communication

HTTPS, TLS, Certificates, and Digital


Signatures
Introduction to TLS/SSL and HTTPS

• Transport Layer Security (TLS) (and its predecessor, Secure


Sockets Layer (SSL)) is a cryptographic protocol designed to
provide communications security over a computer network.
• Its primary aims are privacy (confidentiality), integrity, and authenticity
through the use of cryptography between communicating applications.
• TLS runs "on top of some reliable transport protocol (e.g., TCP)".
• Applications often use TLS as if it were a transport layer, but developers
must actively control initiating TLS handshakes and handling exchanged
certificates.
• While used in various applications like email, instant messaging, and VoIP,
TLS's most publicly visible use is in securing HTTP traffic, which constitutes
the HTTPS protocol.
The Role of Digital Certificates

• A digital certificate serves to certify the ownership of a public


key by the named subject of the certificate.
• It also indicates certain expected usages of that key.
• Digital certificates allow other parties (relying parties) to rely
upon signatures or assertions made by the private key that
corresponds to the certified public key.
• In the context of TLS, certificates are crucial for
authentication, certifying the integrity of a website and
confirming that visitors are connecting to the correct server.
The Role of Certificate Authorities
(CAs)
• TLS typically relies on a set of trusted third-party certificate authorities
(CAs) to establish the authenticity of certificates.
• Trust in CAs is usually anchored in a list of certificates distributed with user
agent software (like web browsers).
• Certificate authorities are necessary in a Public Key Infrastructure (PKI) to
verify the relationship between a certificate and its owner, and to
generate, sign, and manage certificate validity.
• Choosing X.509 certificates means CAs are needed for this verification
process.
• However, CAs can also be a weak point from a security standpoint,
potentially allowing man-in-the-middle (MITM) attacks if the CA
cooperates or is compromised.
How TLS Provides Security

• Privacy (Confidentiality): Data is encrypted using a symmetric-


key algorithm. The symmetric keys are generated uniquely for
each connection based on a shared secret negotiated at the
start of the session.
• Authentication: The identity of the communicating parties can
be authenticated using public-key cryptography. Server
authentication is required, while client authentication is
optional.
• Integrity: Each message includes a message integrity check
using a message authentication code (MAC). This prevents
undetected loss or alteration of the data during transmission.
The TLS Handshake - Establishing a
Secure Connection
• Before exchanging information, the client and server
negotiate a stateful connection using a handshaking
procedure.
• This handshake uses an asymmetric cipher to establish cipher
settings and a session-specific shared key for symmetric
encryption.
• All key data is derived from a "master secret", which is
computed from random numbers generated by both client
and server and a "PreMasterSecret".
Digital Signatures in the Handshake

• Digital signatures are used as part of the authentication process


during the TLS handshake.
• When a client authenticates, it sends a CertificateVerify message.
• This message is a signature over the previous handshake
messages using the client's certificate's private key.
• The server can then verify this signature using the client's
certificate's public key.
• This process lets the server know that the client has access to the
private key corresponding to the certificate and therefore owns
the certificate.
Simple Real-Life Scenario: Basic Website
Connection (HTTPS)

• 1. ClientHello: Web browser connects to a TLS-enabled server and sends supported


TLS version, random number, cipher suites, and compression methods.
• 2. ServerHello: Server responds with selected protocol version, cipher suite, and its
own random number.
• 3. Server Certificate: Server sends its digital certificate with its public encryption key.
• 4. Client Verification: Browser validates the server's certificate.
• 5. ClientKeyExchange: Browser generates PreMasterSecret, encrypts it with server's
public key, and sends it.
• 6. Key Computation: Both compute a master secret from random values and
PreMasterSecret.
• 7. Handshake Completion: Confirm switch to new cipher suite and keys.
• 8. Secured Data Exchange: Communication is encrypted using session keys, each
message includes a MAC for integrity checking.
Challenges in certificate
Revocation.
Certificate Revocation Mechanisms:
• Certificate Revocation Lists (CRLs): Lists of revoked certificates published by CAs. Clients
must download and check these lists to verify certificate validity.
• Online Certificate Status Protocol (OCSP): Allows clients to query the CA in real-time to check
the revocation status of a specific certificate.

Practical Issues:
• Latency and Privacy Concerns: OCSP checks can introduce latency and may expose user
browsing habits to CAs.
• Availability: If OCSP responders are unavailable, browsers often default to a "soft-fail,"
accepting the certificate without confirmation of its validity.
• Ineffectiveness: Due to these issues, certificate revocation mechanisms often fail to prevent
the use of compromised certificates in practice.

Implications:
• Attackers with access to a compromised certificate and its private key can perform man-in-
the-middle attacks, as browsers may not effectively check revocation status.
Getting a Root CA Accepted in
Systems and Browsers.
Certification Requirements:
• CAs must be audited and certified by recognized authorities like WebTrust.
• They must demonstrate secure key management, proper validation
processes, and adherence to strict operational policies.
Browser and OS Trust Stores:
• Operating Systems: Maintain their own list of trusted root CAs.
• Browsers: Some, like Firefox, maintain their own trust stores, while others
rely on the OS's trust store.
Inclusion Process:
• CAs must apply to each browser and OS vendor separately, providing
evidence of compliance with their specific requirements.
• The process is rigorous to ensure that only trustworthy CAs are included,
maintaining the integrity of the PKI system.

You might also like