jojo/routers/web/auth
Gusted 37973790dc fix: verify code challenge of S256
We do not know for sure, but it is quite likely someone assumed implicit
fallthrough. This meant that if someone used S256 for PKCE, it simply
did not verify the code challenge and always accepted it.

PKCE only started working recently as it was broken for a long time
already, forgejo/forgejo!8678
2026-03-06 11:20:50 -07:00
..
2fa.go [v11.0/forgejo] fix: consistently enforce 2FA on OpenID 2.0 (#9096) 2025-08-30 18:57:11 +02:00
auth.go [v11.0/forgejo] fix: consistently enforce 2FA on OpenID 2.0 (#9096) 2025-08-30 18:57:11 +02:00
auth_test.go [v11.0/forgejo] chore: branding import path (#7354) 2025-03-27 20:13:05 +00:00
linkaccount.go fix(sec): consider webauthn for external login 2025-05-02 07:31:20 +02:00
main_test.go [v11.0/forgejo] chore: branding import path (#7354) 2025-03-27 20:13:05 +00:00
oauth.go fix: verify code challenge of S256 2026-03-06 11:20:50 -07:00
oauth_test.go [v11.0/forgejo] chore: branding import path (#7354) 2025-03-27 20:13:05 +00:00
openid.go [v11.0/forgejo] fix: consistently enforce 2FA on OpenID 2.0 (#9096) 2025-08-30 18:57:11 +02:00
password.go [v11.0/forgejo] fix: allow unactivated users to send recovery mails (#9516) 2025-10-03 09:50:03 +02:00
webauthn.go [v11.0/forgejo] fix: consistently enforce 2FA on OpenID 2.0 (#9096) 2025-08-30 18:57:11 +02:00