gitea: U2F doesn't work on Chrome 74

Gitea version (or commit ref): 1.8.0
Git version: 2.21.0
Operating system: Archlinux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes
- No
- Not relevant
Log gist:

Description

U2F does not work on login, but registration works well. Client is Chrome on MacOS.

Screenshots

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 4
Comments: 22 (11 by maintainers)

Most upvoted comments

I get the same now - worked before. Strange thing is when I try to register a new key I get:

Could not read your security key. Please make sure to use the correct, encrypted (https://) URL.

But my page is correctly served from https. The TLS connection is terminated in nginx in front of gogs. nginx config:

  proxy_set_header Host            $host;
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header X-Real-IP       $remote_addr;
  proxy_set_header X-Scheme        $scheme;

nougad on Apr 28, 2019

For me it broke when I updated Chrome to version 74. Downgrading to 73 solves the problem. I can reproduce this on both Linux (Ubuntu 18.04, Chromium) and OSX (Mojave, Chrome). Firefox works on both platforms

sh0rez on May 1, 2019