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

Please whitelist Safari for U2F #9922

Closed
5 tasks
clstrco opened this issue Jan 21, 2020 · 5 comments
Closed
5 tasks

Please whitelist Safari for U2F #9922

clstrco opened this issue Jan 21, 2020 · 5 comments

Comments

@clstrco
Copy link

clstrco commented Jan 21, 2020

  • Gitea version (or commit ref):

Gitea version 1.10.3 built with GNU Make 4.1, go1.13.6 : bindata

  • Git version:

git version 2.17.1

  • Operating system:

macOS 10.15.2

Safari 13.0.4

  • Database (use [x]):
    • [x ] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • [x ] Yes (provide example URL):

https://try.gitea.io/user/settings/security

  • No
  • Not relevant
  • Log gist:

Description

Although caniuse suggests modern Safari supports U2f (and I have verified this works with Github) gitea seems to blacklist it as a browser. When I try to add a key it say:

Could not read your security key.
Your browser does not support U2F security keys.

Screenshots

image

@lunny
Copy link
Member

lunny commented Jan 22, 2020

Have you tried with a local gitea instance or try site?

@clstrco
Copy link
Author

clstrco commented Jan 22, 2020

Have you tried with a local gitea instance or try site?

Yes, I've attempted both.

I've had success with the demos here: https://webauthn.io using this safari.

@techknowlogick
Copy link
Member

related ticket: #6892

@stale
Copy link

stale bot commented Mar 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Mar 22, 2020
@stale
Copy link

stale bot commented Apr 5, 2020

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Apr 5, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants