#471: Securer Contexts
Discussions
2020-02-10
David: We have none of the assignees here...
David: Maybe a face-to-face issue? But will we have time to discuss in depth there?
Tess: At least push it out a week until we have the assignees
David: We have none of the assignees here...
David: Maybe a face-to-face issue? But will we have time to discuss in depth there?
Tess: At least push it out a week until we have the assignees
OpenedFeb 5, 2020
Hello TAG!
I'm requesting a TAG review of Secur<em>er</em> Contexts.
Secure Context's threat model encompasses the transport layer. This proposal would extend it to include attackers with the ability to inject code into a victim's document (by tricking either the server or client-side code), and attackers who seek to include a victim's resources into a context where they may be vulnerable to side-channel attacks. This extension of the threat model would allow us to likewise extend the
[SecureContext]
IDL attribute to express new requirements for new mitigations.Further details:
You should also know that the TAG was the venue in which Secure Contexts began (hello, @diracdeltas!).
We'd prefer the TAG provide feedback as (please delete all but the desired option) review feedback as a comment in this issue, @-notifying @mikewest.
:heart: