-
-
Notifications
You must be signed in to change notification settings - Fork 694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify 14.3.1 #2821
Comments
Concern comes from the fact that whetever is on the client side is under user control.
|
I think the aim here is that there is client side code that deletes client side data. It is in the user's interested to this and if an attacker already has control of the client side then they already have the data anyway so it is game over |
May one interpret, that if the connection is lost, then immediate clean-up must be triggered? |
So no, that is going to cause a problem. The implication of the requirement is that when the user logs out or when it is expected that a client side data clean would be triggered, the app cannot just rely on the Clear-Site-Data header but rather needs to have client side mechanisms to handle that as well |
Yes, my question was, that if someone only focuses on the last sentence, may it be interpreted like that. |
Ok, I understand. Suggestion: "[MODIFIED] Verify that authenticated data is cleared from client storage, such as the browser DOM, after the client or session is terminated. The "Clear-Site-Data header" may be able to help with this but the client-side should also be able to clear up if the server connection is not available when the session is terminated." |
PR with tiny modification
|
Current:
@elarlang said:
Not sure what the concern is here?
The text was updated successfully, but these errors were encountered: