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

clarification - 4.1.2 Secure transaction API details #80

Closed
vgalindo opened this issue Jul 1, 2016 · 2 comments
Closed

clarification - 4.1.2 Secure transaction API details #80

vgalindo opened this issue Jul 1, 2016 · 2 comments
Assignees
Labels

Comments

@vgalindo
Copy link
Collaborator

vgalindo commented Jul 1, 2016

In the sentence :
'use cases are not highly sensitive in terms of transaction context confidentiality, which means that standard SOP rules are considered sufficient without any need for end-to-end encryption (like secure messaging).'

--> 2 remarks
The CG should wonder is we want to have this API being operated only in the context of Priviledged Context [https://www.w3.org/TR/secure-contexts/] or not.
In addition, the usage of 'secure messaging', looks very smart card centric and does not refer to the ususal working in W3C specifications (HTTPS, for ex).

@sbahloul
Copy link
Collaborator

To be reviewed today

@sbahloul
Copy link
Collaborator

Add in 6. TODO

sbahloul pushed a commit that referenced this issue Jul 26, 2016
sbahloul pushed a commit that referenced this issue Jul 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants