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

[Security] UI guidelines for pairing and trusted/untrusted data #118

Closed
markafoltz opened this issue Oct 18, 2018 · 2 comments
Closed

[Security] UI guidelines for pairing and trusted/untrusted data #118

markafoltz opened this issue Oct 18, 2018 · 2 comments
Labels
F2F security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. v1-spec

Comments

@markafoltz
Copy link
Contributor

Follow up from Berlin F2F, slide 84 of the presentation

This issue covers the preparation of UI guidelines to help user agents convey the authentication state and pairing action (passcode entry) for Open Screen devices to users.

@markafoltz markafoltz added security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. v1-spec labels Oct 18, 2018
@markafoltz markafoltz added F2F and removed F2F labels May 2, 2019
@markafoltz
Copy link
Contributor Author

There's one more guideline I'll prepare a PR about so it can be reviewed separately. After that we can assess if the considerations are sufficient, at least for the 1.0 spec.

@markafoltz
Copy link
Contributor Author

Closing based on having a list of UI guidelines for pairing and trusted/untrusted data. Might still refine terminology etc. based on further reviews and discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F2F security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. v1-spec
Projects
None yet
Development

No branches or pull requests

1 participant