bad line length character Error when no SSH key #4808

New Issue

GiteaMirror · 2025-11-02T06:03:30-06:00

GiteaMirror commented

2025-11-02 06:03:30 -06:00

Originally created by @antonio-fr on GitHub (Feb 7, 2020).

On gitea master branch (commit 11995bf2ee).
When a the user has no SSH key registered. The ssh access tells fatal: protocol error: bad line length character: git@
How can we change the effect to be more user friendly about this error message?

Originally created by @antonio-fr on GitHub (Feb 7, 2020). On gitea master branch (commit 11995bf2ee2572995e7bc17b2b889ae33474f36c). When a the user has no SSH key registered. The ssh access tells `fatal: protocol error: bad line length character: git@` How can we change the effect to be more user friendly about this error message?

GiteaMirror added the type/question issue/stale labels 2025-11-02 06:03:30 -06:00

GiteaMirror closed this issue

2025-11-02 06:03:30 -06:00

GiteaMirror commented

2025-11-02 06:03:31 -06:00

@stale[bot] commented on GitHub (Apr 7, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 7, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:03:31 -06:00

@zeripath commented on GitHub (Apr 7, 2020):

Oh sorry I think we missed this one.

I'm not completely clear how you're receiving this error. Could you give me a longer explanation of how to reproduce this?

@zeripath commented on GitHub (Apr 7, 2020): Oh sorry I think we missed this one. I'm not completely clear how you're receiving this error. Could you give me a longer explanation of how to reproduce this?

GiteaMirror commented

2025-11-02 06:03:31 -06:00

@antonio-fr commented on GitHub (Apr 9, 2020):

Thanks. First of all, I'm not sure this is an issue with Gitea. This might be at the sshd or git side. This is more a support question.

The issue is when using gitea in a Linux sshd server. Users auth themself using git@server using SSH protocol. When a user auth, using an agent and a git desktop client, with an unknown or invalid key (a SSH key which is not corresponding to any gitea users), the server responds with the following error message : fatal: protocol error: bad line length character: git@.
I'd like to know, if one got any idea, what is wrong with my server config. Because this message is not explicit at all, and I expect some message like 'wrong user key" or "unknown user".

@antonio-fr commented on GitHub (Apr 9, 2020): Thanks. First of all, I'm not sure this is an issue with Gitea. This might be at the sshd or git side. This is more a support question. The issue is when using gitea in a Linux sshd server. Users auth themself using git@server using SSH protocol. When a user auth, using an agent and a git desktop client, with an unknown or invalid key (a SSH key which is not corresponding to any gitea users), the server responds with the following error message : `fatal: protocol error: bad line length character: git@.` I'd like to know, if one got any idea, what is wrong with my server config. Because this message is not explicit at all, and I expect some message like 'wrong user key" or "unknown user".

GiteaMirror commented

2025-11-02 06:03:31 -06:00

@stale[bot] commented on GitHub (Jun 9, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jun 9, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:03:32 -06:00

@stale[bot] commented on GitHub (Jun 23, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 23, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 07:36:15 -06:00

issues export function #7777

GiteaMirror referenced this issue

2025-11-02 08:01:39 -06:00

【Feature Request】Can I export the issue to excel #8301

Sign in to join this conversation.