Skip to content

Gitea refuses SSH connections when using valid public keys #12667

Closed
@bkraul

Description

@bkraul
  • Gitea version (or commit ref): afd89b1 (and 58f57b3)
  • Git version: 1.13.0+dev-496
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL): N/A, SSH issue.
    • No
    • Not relevant
  • Log gist:

Description

Commits afd89b1 (and 58f57b3) have an issue where all public SSH keys are rejected. This does not happen with commit f8601f3. I have been able to test this on try.gitea.io, and this is the error I get:

git clone [email protected]:bkraul/TestProject.git
Cloning into 'TestProject'...
fatal: 'bkraul/TestProject.git' does not appear to be a git repository
Gitea: Internal error
Failed to execute git command: exit status 128
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

The repository does exist and the public SSH key is valid.

Screenshots

image
image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions