Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use (top-level site, embedded site) permissions #147

Closed
johannhof opened this issue Dec 15, 2022 · 0 comments
Closed

Use (top-level site, embedded site) permissions #147

johannhof opened this issue Dec 15, 2022 · 0 comments
Assignees
@johannhof
Labels
resolve before graduation These issues need to be resolved before the spec graduates from the CG

Comments

@johannhof
Copy link
Member

There seems to be consensus that given the security properties of per-frame rSA it's reasonable to go back to (site, site) as the permission key. This would have the advantage that adjacent same-site iframes would be able to observe when storage access was available, without exposing these iframes to immediate storage access. It would also codify the user-visible permission grant level that most browsers will likely apply.
@johannhof johannhof added the resolve before graduation These issues need to be resolved before the spec graduates from the CG label Dec 15, 2022
@johannhof johannhof self-assigned this Dec 15, 2022
@johannhof johannhof mentioned this issue Dec 15, 2022
Merged
3 tasks
johannhof added a commit to johannhof/storage-access that referenced this issue Jan 23, 2023
@johannhof
Switch to (top-level site, embedded site) keying (closes privacycg#147,
578483d 
privacycg#156)

This updates the permission key for storage-access to (site, site), and
also removes the concept of the "partitioned storage key", which was
origin-keyed as well. The storage key was only used for running the
implementation-defined steps that are supposed to be removed as of privacycg#156.
@mreichhoff mreichhoff mentioned this issue Mar 16, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@johannhof johannhof

Labels
resolve before graduation These issues need to be resolved before the spec graduates from the CG
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@johannhof