#1 ·
Hey everyone, hope you're all doing well.
I was wondering if anyone here could break some of these concepts down for me in plain English. I've tried digging through Google for definitions, but honestly, most of it just goes over my head. I think I just need a good, old-fashioned, "explain it like I'm five" kind of breakdown...
Here’s what I’m stuck on:
What exactly is an internet socket? Like, what is it actually made of...???
Can someone explain DDoS attacks? What are the main things to look for during one, and what's the deal with those sender addresses when an attack is happening?
The whole thing about secure communication between a client and a server... why does it even matter, and at what specific point do we actually need to start worrying about protection?
A quick summary of how digital signatures and hashing work together??
Then there's algorithms and keys. One version says with asymmetric encryption, everyone knows the public key, but with symmetric, it's different... because if everyone gets hold of that symmetric key, then everything is out in the open and security is gone. My big question is: how do you actually protect that key, or better yet, how do you safely get it to the other person??
And finally, comparing HTTP vs HTTPS. How does a standard HTTP connection work—where you send a request with headers to a server and get a response back—and then where does the security layer kick in for HTTPS? How would I go about documenting that process?
I was wondering if anyone here could break some of these concepts down for me in plain English. I've tried digging through Google for definitions, but honestly, most of it just goes over my head. I think I just need a good, old-fashioned, "explain it like I'm five" kind of breakdown...
Here’s what I’m stuck on:
What exactly is an internet socket? Like, what is it actually made of...???
Can someone explain DDoS attacks? What are the main things to look for during one, and what's the deal with those sender addresses when an attack is happening?
The whole thing about secure communication between a client and a server... why does it even matter, and at what specific point do we actually need to start worrying about protection?
A quick summary of how digital signatures and hashing work together??
Then there's algorithms and keys. One version says with asymmetric encryption, everyone knows the public key, but with symmetric, it's different... because if everyone gets hold of that symmetric key, then everything is out in the open and security is gone. My big question is: how do you actually protect that key, or better yet, how do you safely get it to the other person??
And finally, comparing HTTP vs HTTPS. How does a standard HTTP connection work—where you send a request with headers to a server and get a response back—and then where does the security layer kick in for HTTPS? How would I go about documenting that process?