HTTPS stands for Hypertext Transfer Protocol Secure which is just an extension of the HTTP (Hypertext Transfer Protocol). The HTTPS is the more secure data transmission factor that uses Transport Layer Security (TLS) to address the encrypted data. This means that if a hacker tries to get into the system, all they get is binary data and not valid data.
This is a secure way of data transmission.
HTTPS starts with the client and the server. When they form a TCP (Transmission Control Protocol) connection, a server receives a “client hello” from the client which embeds the set of required encryption algorithms like Cipher suites and the latest TLS version where it can reside.
After that, the server generates a “server hello” message to let the client know whether it can support the given algorithms or the TLS version.
Immediately after, the client also picks up the SSL certificate with a public key, hostname, expiry dates, etc. This was sent by the server so that the client would validate it and generate a session key. This session key is encrypted using the public key and then the server key gets this session key which it will decrypt using the private key.
Now we get to see symmetric encryption since both the client and the server hold the same session key. The encrypted data is transmitted in a secure bi-directional channel.
This is far more secure than what we have previously seen with the HTTP protocols.
However, it still uses symmetric encryption when the asymmetric gives far more advantage to our cause. There are a few reasons for this,
Symmetric encryption gives no security if the server tries to send the encrypted data back to the client since anyone will be able to decrypt it using the one session key. But that is not the case in asymmetric encryption.
When we need to transmit data in long sessions, asymmetric encryption gives us many mathematical overheads. This is avoided when we use symmetric encryption.
Wrapping up, HTTPS is a secure extension of HTTP and now, it is more prevalent than ever.
pragyaasapkota
/
System-Design-Concepts
A repo with some system design concepts.
System Design
Systems design is the process of defining elements of a system like modules, architecture, components and their interfaces and data for a system based on the specified requirements.
This is a index for the concepts of system.
If you wish to open these in a new tab, Press CTRL+click
| S.N. | Table of Content |
|---|---|
| 1. | Caching |
| 2. | Network Protocols |
| 3. | Storage: The Underrated Topic |
| 4. | Latency and Throughput |
| 5. | System Availability |
| 6. | Leader Election |
| 7. | Proxies |
| 8. | Load Balancing |
| 9. | Endpoint Protection |
| 10. | HTTPS: Is it better than HTTP? |
| 11. | Polling and Streaming |
| 12. | Long Polling |
| 13. | Hashing |
| 14. | CAP Theorem |
| 15. | PACELC Theorem |
| 16. | Messaging and Pub-Sub |
| 17. | Database |
| 18. | Logging, Monitoring, and Alerting |
| 19. | Distributed System |
| 20. | Scaling |
| 21. | Event Driven Architecture (EDA) |
Thank you!!!
I hope this article was helpful to you.
Please don’t forget to follow me!!!
Any kind of feedback or comment is welcome!!!
Thank you for your time and support!!!!
Keep Reading!! Keep Learning!!!
Top comments (2)
This is wrong!, I assume you made a simple typo there, as claimed decryption using public key is not right. Also mind there is no public/private keys term defined for symmetric encryption, as one key(aka "secret key") is used for both encryption/decryption
Thank you for informing me. You were right. It as a typo and I have corrected it now.
You can check ot once again.