generated from martinthomson/internet-draft-template
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Adding Cross-Site Ancestor Chain bit #11
Comments
Closing this issue because it's now been enabled by default in Chrome. |
---------- Forwarded message ---------
Gönderen: Aaron Selya ***@***.***>
Date: 8 Eki 2024 Sal 23:33
Subject: Re: [explainers-by-googlers/CHIPS-spec] Adding Cross-Site Ancestor
Chain bit (Issue #11)
To: explainers-by-googlers/CHIPS-spec ***@***.***>
Cc: Subscribed ***@***.***>
Closing this issue because it's now been enabled by default in Chrome
<privacycg/CHIPS#40 (comment)>.
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BA5EAAGC2OW5LLCUXXFFXZTZ2Q6SHAVCNFSM6AAAAABPTCHRDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBQG43DQOBUHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
---------- Forwarded message ---------
Gönderen: Nihal Celik ***@***.***>
Date: 8 Eki 2024 Sal 23:37
Subject: Re: [explainers-by-googlers/CHIPS-spec] Adding Cross-Site Ancestor
Chain bit (Issue #11)
To: explainers-by-googlers/CHIPS-spec <
***@***.***>
Cc: explainers-by-googlers/CHIPS-spec ***@***.***>,
Subscribed ***@***.***>
…---------- Forwarded message ---------
Gönderen: Aaron Selya ***@***.***>
Date: 8 Eki 2024 Sal 23:33
Subject: Re: [explainers-by-googlers/CHIPS-spec] Adding Cross-Site Ancestor
Chain bit (Issue #11)
To: explainers-by-googlers/CHIPS-spec ***@***.***>
Cc: Subscribed ***@***.***>
Closing this issue because it's now been enabled by default in Chrome
<privacycg/CHIPS#40 (comment)>.
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BA5EAAGC2OW5LLCUXXFFXZTZ2Q6SHAVCNFSM6AAAAABPTCHRDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBQG43DQOBUHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
---------- Forwarded message ---------
Gönderen: Nihal Celik ***@***.***>
Date: 18 Eki 2024 Cum 13:31
Subject: Re: [explainers-by-googlers/CHIPS-spec] Adding Cross-Site Ancestor
Chain bit (Issue #11)
To: explainers-by-googlers/CHIPS-spec <
***@***.***>
Cc: explainers-by-googlers/CHIPS-spec ***@***.***>,
Subscribed ***@***.***>
…---------- Forwarded message ---------
Gönderen: Nihal Celik ***@***.***>
Date: 8 Eki 2024 Sal 23:37
Subject: Re: [explainers-by-googlers/CHIPS-spec] Adding Cross-Site Ancestor
Chain bit (Issue #11)
To: explainers-by-googlers/CHIPS-spec <
***@***.***>
Cc: explainers-by-googlers/CHIPS-spec ***@***.***>,
Subscribed ***@***.***>
---------- Forwarded message ---------
Gönderen: Aaron Selya ***@***.***>
Date: 8 Eki 2024 Sal 23:33
Subject: Re: [explainers-by-googlers/CHIPS-spec] Adding Cross-Site Ancestor
Chain bit (Issue #11)
To: explainers-by-googlers/CHIPS-spec ***@***.***>
Cc: Subscribed ***@***.***>
Closing this issue because it's now been enabled by default in Chrome
<privacycg/CHIPS#40 (comment)>.
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BA5EAAGC2OW5LLCUXXFFXZTZ2Q6SHAVCNFSM6AAAAABPTCHRDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBQG43DQOBUHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed in the Privacycg, we are looking to add a cross-site ancestor chain bit to CHIPS to address the potential for click jacking attacks in an A->B->A context and align the keying of CHIPS with storage the storage partition key.
The text was updated successfully, but these errors were encountered: