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

Requirement: Security context of calling page #3

Closed
cyberphone opened this issue Jul 25, 2016 · 4 comments
Closed

Requirement: Security context of calling page #3

cyberphone opened this issue Jul 25, 2016 · 4 comments

Comments

@cyberphone
Copy link

It seems reasonable that invoked applications inherit the security context of the calling Web page including:

  • URL
  • HTTPS Certificate

Through this applications will be able showing (in a trustworthy way) invocation domain etc.

@aswan
Copy link

aswan commented Aug 10, 2016

As with issue #2, this issue is either meant for a different project (direct access from content to native applications) or based on a flawed assumption (browser extension actions always being connected to a specific "calling page")

@cyberphone
Copy link
Author

I hope the updated issue #2 clears this.

@frivoal
Copy link
Member

frivoal commented Sep 9, 2016

This is a tentative resolution of the CG. See the minutes of the discussion. If no dissenting opinion is expressed here within 10 days, this will be considered the consensus of the CG.

As this is connected to issue #2 which the CG proposes to close as out of scope, this seems also to be out of scope for this Community Group. The appropriate forum is likely to be the WebPlatform Working Group or the WICG. The security implications of the proposal are also not fully clear, but do seem problematic. The tentative consensus is to close the proposal.

@frivoal
Copy link
Member

frivoal commented Sep 27, 2016

See also #6

@frivoal frivoal closed this as completed Sep 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants