Enable X-Gitea-OTP header for git operations about gitea

[KN4CK3R]

That sounds really exhausting because the OTP always needs to be refreshed. Why not use a PAT instead of the normal password?

[Kwonunn]

This is just for use in cases where I'm fetching a project once onto a server I don't want to set up SSH on.

Using tokens for this would either require making a fresh token every time which is annoying, or having one to always use which is a security hole.

[techknowlogick]

This is quite interesting. On one hand user/pass auth for api/git operations are being depreciated, but it does give the idea of otp with scoped tokens 🤔

[Kwonunn]

Is Gitea planning to deprecate http entirely for git operations?

[KN4CK3R]

No, only the combination with username and password.

[Kwonunn]

Why, if I may ask? I know GitHub has stopped allowing it but I'm not quite sure why.

[KN4CK3R]

Because the username/password combination should be used in less places in favor of configurable tokens.

[Kwonunn]

I see. Then, perhaps another method is more appropriate.

Maybe we could add a quick token button in this menu

which would generate a temporary personal access token scoped specifically to that repository and with read-only access, which you could use once to clone the repository somewhere?

[JakobDev]

No, only the combination with username and password.

Why?

[KN4CK3R]

No, only the combination with username and password.

Why?

#28968 (comment)
https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/#background

[Kwonunn]

I see. Then, perhaps another method is more appropriate.

Maybe we could add a quick token button in this menu which would generate a temporary personal access token scoped specifically to that repository and with read-only access, which you could use once to clone the repository somewhere?

Should I make a new feature request for this new idea and just leave the http OTP thing?

[JakobDev]

Not beeing able to use Username/Password could be a problem for one time contributors