This article explains why HTTP is insecure—prone to eavesdropping, tampering, and identity spoofing—and how HTTPS uses symmetric and asymmetric encryption, hash functions, digital certificates, and a four‑step SSL/TLS handshake to provide confidentiality, integrity, and authentication for web traffic.
This tutorial explains China’s electronic‑seal regulations, shows how to generate a CA‑based X.509 certificate and a custom seal image with BouncyCastle, and demonstrates signing a PDF in Java using iText 5 to embed a visible seal and a verifiable digital signature.
HTTPS secures web traffic by combining symmetric and asymmetric encryption, digital signatures, and certificate authorities within the TLS protocol to ensure confidentiality, integrity, authentication, and non‑repudiation, replacing insecure HTTP and becoming mandatory for modern browsers, servers, and platforms despite earlier concerns about cost and complexity.
This article walks through a step‑by‑step reconstruction of HTTPS’s design, explaining why both symmetric and asymmetric encryption are needed, how key exchange is negotiated, and how digital certificates and signatures solve the trust problem in secure web communication.
This article reconstructs the design of HTTPS step by step, explaining why both symmetric and asymmetric encryption are required, how key negotiation works, the role of digital certificates and certificate authorities, and the underlying security mechanisms that protect client‑server communication.
This article explains why HTTP is insecure, outlines the four core principles of secure communication, and details how HTTPS uses symmetric encryption, asymmetric encryption, digital certificates, and signatures to establish confidentiality, integrity, authentication, and non-repudiation for safe data transmission.
This article explains why plain HTTP is insecure, outlines the four fundamental principles of secure communication, and details how HTTPS uses symmetric encryption, asymmetric encryption, digital certificates, and digital signatures to establish confidentiality, integrity, authentication, and non-repudiation for web traffic.
HTTPS combines HTTP with SSL/TLS to protect data through encryption, integrity checks, and authentication, using asymmetric keys during the handshake to negotiate symmetric encryption, digital signatures, certificates, and a secure session, ensuring safe client‑server communication.
This article explains why HTTP is insecure, demonstrates a plain‑text attack using Wireshark, and then details the encryption types, certificate issuance, digital signatures, and the combined asymmetric‑symmetric handshake that make HTTPS a secure protocol for web communication.
This article reconstructs the design of HTTPS step by step, explaining why both symmetric and asymmetric encryption are required, how key negotiation works, the role of digital certificates and certificate authorities, and the underlying security concepts that protect client‑server communication.
The article explains the security risks of plain HTTP, introduces symmetric and asymmetric encryption, describes digital certificates, certificate authorities, digital signatures, and how they combine in HTTPS to protect data confidentiality, integrity, and authenticity during web communication.
HTTPS secures web communication by combining symmetric and asymmetric encryption, digital certificates, and signatures, addressing HTTP’s confidentiality, integrity, and authenticity flaws; the article explains these cryptographic concepts, the SSL/TLS handshake steps, and when HTTPS is appropriate despite its performance overhead.
This article reconstructs the design of HTTPS by explaining why symmetric encryption, asymmetric encryption, random numbers, digital certificates, and certificate authorities are combined to securely negotiate a shared secret between a client and a web server, while addressing man‑in‑the‑middle attacks and certificate validation.
This article walks through a step‑by‑step reconstruction of HTTPS design, showing why secure communication requires per‑client symmetric keys negotiated via asymmetric encryption, digital certificates from trusted CAs, and how signatures and random numbers protect against man‑in‑the‑middle attacks.
This article reconstructs the design of HTTPS by starting from a simple chat scenario, explaining why both symmetric and asymmetric encryption are required, how key exchange and digital certificates work, and how the TLS handshake secures client‑server communication.
This article provides a comprehensive overview of HTTPS, explaining its purpose, advantages, and drawbacks, and delves into the underlying cryptographic concepts such as symmetric and asymmetric encryption, hash algorithms, digital signatures, digital certificates, and the detailed SSL/TLS handshake process.
This article explains HTTPS fundamentals, its encryption mechanisms, differences from HTTP, the roles of symmetric and asymmetric cryptography, hash functions, digital signatures, certificate issuance and validation, as well as SSL/TLS protocols, handshake steps, and session resumption techniques that secure web communications.
