mirror of
https://github.com/go-gitea/gitea.git
synced 2024-12-27 10:20:48 +08:00
e0853d4a21
One of the issues holding back performance of the API is the problem of hashing. Whilst banning BASIC authentication with passwords will help, the API Token scheme still requires a PBKDF2 hash - which means that heavy API use (using Tokens) can still cause enormous numbers of hash computations. A slight solution to this whilst we consider moving to using JWT based tokens and/or a session orientated solution is to simply cache the successful tokens. This has some security issues but this should be balanced by the security issues of load from hashing. Related #14668 Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> |
||
---|---|---|
.. | ||
analyze | ||
auth | ||
avatar | ||
base | ||
cache | ||
charset | ||
context | ||
convert | ||
cron | ||
csv | ||
doctor | ||
emoji | ||
eventsource | ||
generate | ||
git | ||
gitgraph | ||
graceful | ||
hcaptcha | ||
highlight | ||
httpcache | ||
httplib | ||
indexer | ||
json | ||
lfs | ||
log | ||
markup | ||
matchlist | ||
metrics | ||
migrations | ||
nosql | ||
notification | ||
options | ||
password | ||
pprof | ||
private | ||
process | ||
public | ||
queue | ||
recaptcha | ||
references | ||
repofiles | ||
repository | ||
secret | ||
session | ||
setting | ||
ssh | ||
storage | ||
structs | ||
svg | ||
sync | ||
task | ||
templates | ||
test | ||
timeutil | ||
translation | ||
typesniffer | ||
upload | ||
uri | ||
user | ||
util | ||
validation | ||
web |