Edit - Information Security Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

You're not addressing how the "shared secret" is kept safe on the client side, e.g. where should it be stored. If you're suggesting to store it the cookie, and enabling HttpOnly, then the client is not going to be able to read the secret from the cookie.

HowieTKL
– HowieTKL

2018-03-14 04:24:10 +00:00
Commented Mar 14, 2018 at 4:24
There isn’t a good way to keep the secret safe on the client side. You’re right, in that HttpOnly cookies may be a bad idea since they wouldn’t be readable, but unless the client side is protected against XSS, this would result in stolen cookies.

user172887
– user172887

2018-03-14 04:41:02 +00:00
Commented Mar 14, 2018 at 4:41

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »