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

Should the spec make it clear that you can loosen "CORS" like restriction for dev purposes? #38

Closed
kenchris opened this issue Feb 5, 2016 · 1 comment
Closed

Should the spec make it clear that you can loosen "CORS" like restriction for dev purposes? #38

kenchris opened this issue Feb 5, 2016 · 1 comment

Comments

@kenchris
Copy link

kenchris commented Feb 5, 2016

Service Workers have something like this:

6 Security Considerations
Service workers should be implemented to be HTTPS-only. The reasons for SSL-only support include:

Better to protect end users from man-in-the-middle attacks
Do good by encouraging HTTPS adoption
Existing "playground" services (e.g. github.io) now work with HTTPS
HTTPS is coming across much more of the web quickly
Devtools can loosen the restriction for development (file://, localhost, etc.)
reillyeon added a commit to reillyeon/webusb that referenced this issue Mar 28, 2017
@reillyeon
Integrate with the Feature Policy specification.
a58d2d2 
The integration with the Feature Policy specification allows us to
disallow (by default) access to this feature by cross-origin iframes
with a standardized mechanism for the top-level document to grant access
to this feature to origins that it trusts.

With this mitigation in place the Allowed Origins descriptors are
removed from the specification. This resolves the question in WICG#49 of
whether access to USB devices should be controlled by the vendor or the
user in the favor of the user.

This resolves issue WICG#82 and obsoletes issues WICG#15 and WICG#38.
reillyeon added a commit to reillyeon/webusb that referenced this issue Mar 28, 2017
@reillyeon
Integrate with the Feature Policy specification.
27ad1f4 
The integration with the Feature Policy specification allows us to
disallow (by default) access to this feature by cross-origin iframes
with a standardized mechanism for the top-level document to grant access
to this feature to origins that it trusts.

With this mitigation in place the Allowed Origins descriptors are
removed from the specification. This resolves the question in WICG#49 of
whether access to USB devices should be controlled by the vendor or the
user in the favor of the user.

This resolves issue WICG#82 and obsoletes issues WICG#15 and WICG#38.
@reillyeon reillyeon mentioned this issue Mar 28, 2017
Merged
reillyeon added a commit to reillyeon/webusb that referenced this issue Mar 29, 2017
@reillyeon
Integrate with the Feature Policy specification.
c964613 
The integration with the Feature Policy specification allows us to
disallow (by default) access to this feature by cross-origin iframes
with a standardized mechanism for the top-level document to grant access
to this feature to origins that it trusts.

With this mitigation in place the Allowed Origins descriptors are
removed from the specification. This resolves the question in WICG#49 of
whether access to USB devices should be controlled by the vendor or the
user in the favor of the user.

This resolves issue WICG#82 and obsoletes issues WICG#15 and WICG#38.
@reillyeon
Copy link
Collaborator

The commit above removes the concept of allowed origins which makes the issue obsolete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@reillyeon @kenchris