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.

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

Expose direct socket APIs via [DirectSocketEnabled]. #28861

Merged
merged 1 commit into from May 7, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented May 6, 2021

This patch introduces a new placeholder IDL extended attribute for the
set of restrictions which might enable us to safely expose direct
sockets, as well as a set of other APIs that have similar
outside-the-web threat models. It then applies that IDL extended
attribute to the existing direct socket IDL files.

For the moment, this imposes two requirements on Direct Sockets:

  1. Opting-into COI via COOP/COEP.
  2. Toggling the kDirectSockets CLI flag.

I expect these requirements to shift in the future, but this is a
reasonable place to start.

Patch 5/5:

  1. https://chromium-review.googlesource.com/c/chromium/src/+/2871670
  2. https://chromium-review.googlesource.com/c/chromium/src/+/2874306
  3. https://chromium-review.googlesource.com/c/chromium/src/+/2874288
  4. This patch.
  5. https://chromium-review.googlesource.com/c/chromium/src/+/2875217

Note that this CL removes the Direct Socket interfaces from the
webexposed test suite. That's a little too complicated to fix in
this CL, but I aim to fix it in https://crbug.com/1206656.

Bug: 1206150
Change-Id: I519e1c5d164c43f5870c45823d08063f4a3af682
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2874890
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#880498}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2874890 branch 5 times, most recently from c16cd6c to def869d Compare May 7, 2021 17:23
This patch introduces a new placeholder IDL extended attribute for the
set of restrictions which might enable us to safely expose direct
sockets, as well as a set of other APIs that have similar
outside-the-web threat models. It then applies that IDL extended
attribute to the existing direct socket IDL files.

For the moment, this imposes two requirements on Direct Sockets:

1.  Opting-into COI via COOP/COEP.
2.  Toggling the kDirectSockets CLI flag.

I expect these requirements to shift in the future, but this is a
reasonable place to start.

Patch 5/5:
1.  https://chromium-review.googlesource.com/c/chromium/src/+/2871670
2.  https://chromium-review.googlesource.com/c/chromium/src/+/2874306
3.  https://chromium-review.googlesource.com/c/chromium/src/+/2874288
4.  This patch.
5.  https://chromium-review.googlesource.com/c/chromium/src/+/2875217

Note that this CL removes the Direct Socket interfaces from the
`webexposed` test suite. That's a little too complicated to fix in
this CL, but I aim to fix it in https://crbug.com/1206656.

Bug: 1206150
Change-Id: I519e1c5d164c43f5870c45823d08063f4a3af682
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2874890
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#880498}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants