ssl - Sense of secure cookie over HTTPS -


What does it mean to encrypt cookies (secure cookies) for HTTPS? As far as I know the complete request in HTTPS is encrypted, do we need additional encryption of cookies?

It relies entirely on your security model For some reasons you still have to encrypt the cookies Why is it needed:

  1. Do you care whether a user of your app receives the content of the cookie? In other words, do you store that thing internally and should not be told to the user?

  2. Do you care that the user tamper with the contents of the cookie? Depending on how you do it, encryption can be a way of obtaining loyalty protection. (Of course, there are other ways too.)

  3. What are the results of the disclosure of cookies? If it is a carrier token, whether it is encrypted or not, will not make much difference, but if there is valuable data in it, then an encrypted attacker may access the browser's stored cookies in some way (regardless of It's an attack on the actual system of attacks or browser hosting through the web). You can still defeat an attacker in other ways, but it can provide some protection in depth.

    The main thing to encrypt a cookie is that you are protecting the user from the cookie (or an attacker who can access that user's data) It is, if you need it.

Comments

Popular posts from this blog

excel vba - How to delete Solver(SOLVER.XLAM) code -

github - Teamcity & Git - PR merge builds - anyway to get HEAD commit hash? -

ios - Replace text in UITextView run slowly -