github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

U2F doesn't work on gitea/gitea:latest docker image #5314

New Issue
Closed
opened 2025-11-02 06:21:15 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 06:21:15 -06:00
Owner
Copy Link

Originally created by @jerheij on GitHub (Apr 27, 2020).

  • Gitea version (or commit ref): docker: gitea/gitea:latest
  • Git version: n/a
  • Client Operating system: Windows 10
  • Client browser: Firefox and Edge
  • Host OS: CentOS 7
  • Host Docker version: Docker CE version 19.03.8
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

When I upgrade my docker container to the newest gitea release (gitea/gitea:latest) the yubikey authentication attempt causes the error attached. When I downgrade the gitea to 1.11.4 (gitea/gitea:1.11.4) the yubikey authentication works without issues.

Screenshots

gitea_u2f_error

Originally created by @jerheij on GitHub (Apr 27, 2020). - Gitea version (or commit ref): docker: gitea/gitea:latest - Git version: n/a - Client Operating system: Windows 10 - Client browser: Firefox and Edge - Host OS: CentOS 7 - Host Docker version: Docker CE version 19.03.8 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] Not relevant ## Description When I upgrade my docker container to the newest gitea release (gitea/gitea:latest) the yubikey authentication attempt causes the error attached. When I downgrade the gitea to 1.11.4 (gitea/gitea:1.11.4) the yubikey authentication works without issues. ## Screenshots ![gitea_u2f_error](https://user-images.githubusercontent.com/14292978/80385774-c6d4b980-88a6-11ea-887c-a025aee4a22d.PNG)
GiteaMirror added the issue/criticalissue/confirmedtype/bug labels 2025-11-02 06:21:15 -06:00
GiteaMirror commented 2025-11-02 06:21:16 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Apr 27, 2020):

Can Confirm for: yubikey with linux(5.6.3) + firefox 75.0 (64-bit)

@6543 commented on GitHub (Apr 27, 2020): Can Confirm for: yubikey with linux(5.6.3) + firefox 75.0 (64-bit)
GiteaMirror commented 2025-11-02 06:21:16 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Apr 27, 2020):

Solo U2F also does not work on master branch on Linux + Firefox

@lafriks commented on GitHub (Apr 27, 2020): Solo U2F also does not work on master branch on Linux + Firefox
GiteaMirror commented 2025-11-02 06:21:16 -06:00
Author
Owner
Copy Link

@rgessner commented on GitHub (May 4, 2020):

Almost the same problem.

But here comes only a very short U2F window (<1sec) and then immediately a fallback to the configured TOTP method.

configuration:
podman (Fedora 32) with gitea/gitea:latest
Browser: Chrome and Firefox

( gitea/gitea:1.11.4 runs without problems)

@rgessner commented on GitHub (May 4, 2020): Almost the same problem. But here comes only a very short U2F window (<1sec) and then immediately a fallback to the configured TOTP method. configuration: podman (Fedora 32) with gitea/gitea:latest Browser: Chrome and Firefox ( gitea/gitea:1.11.4 runs without problems)
GiteaMirror commented 2025-11-02 06:21:16 -06:00
Author
Owner
Copy Link

@CirnoT commented on GitHub (May 4, 2020):

https://github.com/grantila/u2f-api/issues/21
https://github.com/Yubico/libu2f-host/issues/130

The world has generally decided to move towards WebAuthn instead of direct protocol implementations, and so we need to do the same. The library we're using can not do that and seems abandoned.

https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API
https://webauthn.bin.coffee/

@CirnoT commented on GitHub (May 4, 2020): https://github.com/grantila/u2f-api/issues/21 https://github.com/Yubico/libu2f-host/issues/130 The world has generally decided to move towards WebAuthn instead of direct protocol implementations, and so we need to do the same. The library we're using can not do that and seems abandoned. https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API https://webauthn.bin.coffee/
GiteaMirror commented 2025-11-02 06:21:17 -06:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 6, 2020):

Ping @jonasfranz

@kolaente commented on GitHub (May 6, 2020): Ping @jonasfranz
GiteaMirror commented 2025-11-02 06:21:17 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (May 6, 2020):

I've looked into this problem. It seems that $.post(...).success()does not work anymore. The u2f api javascript library we're using is outdated and the new version is not backward-compatible to our implementation. I think it makes no sense to stay with u2f since webauthn is the de-facto new standard. In a first step we should roll out a hot fix regarding the jquery stuff.

@jonasfranz commented on GitHub (May 6, 2020): I've looked into this problem. It seems that `$.post(...).success()`does not work anymore. The u2f api javascript library we're using is outdated and the new version is not backward-compatible to our implementation. I think it makes no sense to stay with u2f since webauthn is the de-facto new standard. In a first step we should roll out a hot fix regarding the jquery stuff.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed issue/critical type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5314
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?