0 views collected around this technical thread.
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.
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.
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.
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 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.