-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Docker root setup ssh cert location unexpected #34099
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
Labels
Comments
ManInDark
added a commit
to ManInDark/gitea
that referenced
this issue
Apr 2, 2025
techknowlogick
pushed a commit
that referenced
this issue
Apr 3, 2025
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Apr 3, 2025
techknowlogick
pushed a commit
that referenced
this issue
Apr 3, 2025
Backport #34100 by @ManInDark Fixes #34099. Resolved by checking the `key-cert.pub` location alongside the previously configured location. In case a certificate is already found, this won't change anything, but if there is one in `key-cert.pub` but not in `key_cert`, it'll use that one now. Co-authored-by: ManInDark <[email protected]>
zjjhot
added a commit
to zjjhot/gitea
that referenced
this issue
Apr 8, 2025
* giteaofficial/main: [skip ci] Updated translations via Crowdin docs: add Chinese translations for README files (go-gitea#34132) Keep file tree view icons consistent with icon theme (go-gitea#33921) Make markdown render match GitHub's behavior (go-gitea#34129) Remove dead code: RepoRef (go-gitea#34131) Correctly handle submodule view and avoid throwing 500 error (go-gitea#34121) Use `overflow-wrap: anywhere` to replace `word-break: break-all` (go-gitea#34126) Fix markdown render behaviors (go-gitea#34122) Refactor dropdown ellipsis (go-gitea#34123) Avoid creating unnecessary temporary cat file sub process (go-gitea#33942) Fix discord webhook 400 status code when description limit is exceeded (go-gitea#34084) Refactor markup render to fix various path problems (go-gitea#34114) [skip ci] Updated translations via Crowdin Fix invalid version in RPM package path (go-gitea#34112) also check default ssh-cert location for host (go-gitea#34099) (go-gitea#34100) Fix markdown frontmatter rendering (go-gitea#34102) Get changed files based on merge base when checking `pull_request` actions trigger (go-gitea#34106) Add `last_committer_date` and `last_author_date` for file contents API (go-gitea#32921)
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this issue
Apr 13, 2025
…tea#34100) (cherry picked from commit f8d5494)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In the setup script of root-docker the ssh-certs are only tested to be in a certain location (_cert), but this is
key.pub
the certificate is automatically generated inkey-cert.pub
, at least forOpenSSH_9.9p2, OpenSSL 3.3.3
There is nothing that doesn't actually work, I'd just suggest that the
-cert.pub
should be checked too, since that is where most would try and place the file.Gitea Version
1.23.6
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.47.2
Operating System
alpine
How are you running Gitea?
docker root setup, with separate ip address for gitea
Database
SQLite
The text was updated successfully, but these errors were encountered: