github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-26 22:10:35 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Misleading SSH verify error message (the verification does succeed) #14609

New Issue
Closed
opened 2025-11-02 11:17:26 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 11:17:26 -06:00
Owner
Copy Link

Originally created by @harshitghagre08 on GitHub (Jun 16, 2025).

Originally assigned to: @ozzyozbourne on GitHub.

Description

  • I am trying to do ssh but I am facing error
  • In the ui of the gita is showing that ssh keys are validate also I can see the ssh authorize_key directory
  • But when I check the logs it is showing that it is not validate

Gitea Version

gitea:1.23.8

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

2025/06/12 05:04:45 ...ey/ssh_key_verify.go:38:VerifySSHKey() [E] Unable to validate token signature. Error: ssh: signature did not verify 2025/06/12 05:04:45 ...eb/routing/logger.go:102:func1() [I] router: completed POST /user/settings/keys for , 303 See Other in 15.5ms @ setting/keys.go:46(setting.KeysPost)

Screenshots

Image

Image

Image

Git Version

No response

Operating System

ubuntu lts 24.0.04

How are you running Gitea?

running it on docker container

Database

PostgreSQL

Originally created by @harshitghagre08 on GitHub (Jun 16, 2025). Originally assigned to: @ozzyozbourne on GitHub. ### Description - I am trying to do ssh but I am facing error - In the ui of the gita is showing that ssh keys are validate also I can see the ssh authorize_key directory - But when I check the logs it is showing that it is not validate ### Gitea Version gitea:1.23.8 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist 2025/06/12 05:04:45 ...ey/ssh_key_verify.go:38:VerifySSHKey() [E] Unable to validate token signature. Error: ssh: signature did not verify 2025/06/12 05:04:45 ...eb/routing/logger.go:102:func1() [I] router: completed POST /user/settings/keys for <ip-address>, 303 See Other in 15.5ms @ setting/keys.go:46(setting.KeysPost) ### Screenshots ![Image](https://github.com/user-attachments/assets/cad33546-4eeb-4c36-b32e-213e3fcf9646) ![Image](https://github.com/user-attachments/assets/64f15c35-dbde-4659-9ffa-58519085cc4d) ![Image](https://github.com/user-attachments/assets/23be79f9-2c79-4806-9102-c6bcac1783d7) ### Git Version _No response_ ### Operating System ubuntu lts 24.0.04 ### How are you running Gitea? running it on docker container ### Database PostgreSQL
GiteaMirror added the good first issuetype/bug labels 2025-11-02 11:17:27 -06:00
GiteaMirror commented 2025-11-02 11:17:28 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 16, 2025):

It's an unrelated message, the error message is wrong and should be removed. You can safely ignore it.

@wxiaoguang commented on GitHub (Jun 16, 2025): It's an unrelated message, the error message is wrong and should be removed. You can safely ignore it.
GiteaMirror commented 2025-11-02 11:17:28 -06:00
Author
Owner
Copy Link

@ozzyozbourne commented on GitHub (Jun 16, 2025):

I would like to work on this issue

@ozzyozbourne commented on GitHub (Jun 16, 2025): I would like to work on this issue
GiteaMirror commented 2025-11-02 11:17:28 -06:00
Author
Owner
Copy Link

@harshitghagre08 commented on GitHub (Jun 17, 2025):

It's an unrelated message, the error message is wrong and should be removed. You can safely ignore it.

If it's correct done so why it is asking password after doing the ssh

@harshitghagre08 commented on GitHub (Jun 17, 2025): > It's an unrelated message, the error message is wrong and should be removed. You can safely ignore it. If it's correct done so why it is asking password after doing the ssh
GiteaMirror commented 2025-11-02 11:17:28 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 17, 2025):

If it's correct done so why it is asking password after doing the ssh

99% is that you used wrong SSH port. Gitea's SSH server doesn't use password auth.

@wxiaoguang commented on GitHub (Jun 17, 2025): > If it's correct done so why it is asking password after doing the ssh 99% is that you used wrong SSH port. Gitea's SSH server doesn't use password auth.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label good first issue type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14609
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?