-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal Server Error when access is granted with deploy-key #17412
Comments
Could you change |
in dev mode i get the same four lines in gitea journal
The git client gives me a little bit more infomation
And here is the matching part of gitea.log file
|
The crash is introduced by #17373 (Ensure correct SSH permissions check for private and restricted users), code for When checking with a deploy key, the |
damn! Sorry! |
Unfortunately there was a regression in go-gitea#17373 which missed that the user is not for deploy keys. This leads to a panic when pushing with deploy keys. Fix go-gitea#17412 Signed-off-by: Andrew Thornton <[email protected]>
Backport go-gitea#17434 Unfortunately there was a regression in go-gitea#17373 which missed that the user is not for deploy keys. This leads to a panic when pushing with deploy keys. Fix go-gitea#17412 Signed-off-by: Andrew Thornton <[email protected]>
Unfortunately there was a regression in #17373 which missed that the user is not for deploy keys. This leads to a panic when pushing with deploy keys. Fix #17412 Signed-off-by: Andrew Thornton <[email protected]>
Backport #17434 Unfortunately there was a regression in #17373 which missed that the user is not for deploy keys. This leads to a panic when pushing with deploy keys. Fix #17412 Signed-off-by: Andrew Thornton <[email protected]>
This is a rather major regression. Can we get a quick bugfix release for that please? I had to downgrade to 1.15.4, but 1.15.5 / #17373 are security relevant too... |
Unfortunately there was a regression in go-gitea#17373 which missed that the user is not for deploy keys. This leads to a panic when pushing with deploy keys. Fix go-gitea#17412 Signed-off-by: Andrew Thornton <[email protected]>
Gitea Version
1.15.5
Git Version
2.20.1
Operating System
Debian 10
How are you running Gitea?
pre-build binary gitea-1.15.5-linux-amd64
Database
SQLite
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Description
After update from 1.15.4 to 1.15.5 i noticed that access to the repository with ssh and ssh-keys configured in
Settings -> Deploy Keys
returns a Internal Server Error
Log (git client)
git clone --single-branch --branch master git@myserver:myuser/giteatest.git /tmp/test
Cloning into '/tmp/test'...
Warning: Permanently added 'myserver,myip' (ECDSA) to the list of known hosts.
Gitea: Internal Server Error
Gitea: Internal Server Error
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Log from gitea:
Oct 23 14:41:42 gitea[13029]: 2021/10/23 14:41:42 Started GET /api/internal/serv/command/13/myuser/giteatest?mode=1&verb=git-upload-pack for [::1]:47392
Oct 23 14:41:42 gitea[13029]: 2021/10/23 14:41:42 Completed GET /api/internal/serv/command/13/myuser/giteatest?mode=1&verb=git-upload-pack 500 Internal Server Error in 2.907278ms
Oct 23 14:41:42 gitea[13029]: 2021/10/23 14:41:42 Started POST /api/internal/ssh/log for [::1]:47394
Oct 23 14:41:42 gitea[13029]: 2021/10/23 14:41:42 Completed POST /api/internal/ssh/log 200 OK in 141.16µs
If i add the same ssh-key to my user profile instead of put it to the deploy keys it is possible to clone this repository.
BR
Stefan
Screenshots
No response
The text was updated successfully, but these errors were encountered: