Gusted b76970f2e4 Fix key signature error page (#22229) ... - When the GPG key contains an error, such as an invalid signature or an email address that does not match the user.A page will be shown that says you must provide a signature for the token. - This page had two errors: one had the wrong translation key and the other tried to use an undefined variable [`.PaddedKeyID`](e81ccc406b/models/asymkey/gpg_key.go (L65-L72)), which is a function implemented on the `GPGKey` struct, given that we don't have that, we use [`KeyID`](e81ccc406b/routers/web/user/setting/keys.go (L102)) which is [the fingerprint of the publickey](https://pkg.go.dev/golang.org/x/crypto/openpgp/packet#PublicKey.KeyIdString) and is a valid way for opengpg to refer to a key. Before:  After:  Co-authored-by: zeripath <art27@cantab.net>		2022-12-30 12:53:05 +08:00
..
security	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
account.go	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
account_test.go	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
adopt.go	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
applications.go	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
keys.go	Fix key signature error page (#22229)	2022-12-30 12:53:05 +08:00
main_test.go	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
oauth2.go	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
oauth2_common.go	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
packages.go	Update gitea-vet to check FSFE REUSE (#22004)	2022-12-02 22:14:57 +08:00
profile.go	refactor some functions to support ctx as first parameter (#21878)	2022-12-03 10:48:26 +08:00