Alice and Bob are the traditional protagonists of an encryption scenario. Eve is the traditional eavesdropper.
HTTPS is secure, using end-to-end encryption for the message body.
Public key is really powerful, but it's also slow. So what happens in practice is to use public key at the beginning in order to exchange as session key, that is then used to encrypt the rest of the conversation (session).
Consider how you would print a quotation mark in Python. Hmm. A string ends when you get to a quotation mark, so we need some "escape" sequence, like \"
Similarly, since HTML elements start with an angle bracket, it's hard to display one on the page. That's where < comes in.
<img src=""http://nasty.xxx/""> <script>window.location = 'http://nasty.xxx'</script> <em onmouseover=""window.location = 'http://nasty.xxx';""> mouse over me!</em>
We'll do a demo today
Flask does this for us automatically. However, there are time when we need to bypass those automatic protections, so it's important to understand what it's protecting us from.
Files that are on your laptop or on the server but that are not in the GIT repo. For example, ~/.my.cnf