Adding a deploy key from copy/paste doesn't work #3610

New Issue

GiteaMirror · 2025-11-02T05:19:24-06:00

GiteaMirror commented

2025-11-02 05:19:24 -06:00

Originally created by @bohwaz on GitHub (Jul 17, 2019).

Gitea version (or commit ref): 1.8.3

Description

If I do a cat ~/.ssh/id_rsa.pub and copy paste it in Gitea to the textarea to add a new deploy key, I get the error "Can not verify your SSH key: extractTypeFromBase64Key: invalid key format: illegal base64 data at input byte 168"

If I remove the line break in the middle, it works.

It seems that Gitea doesn't handle line returns inside keys.

Originally created by @bohwaz on GitHub (Jul 17, 2019).   - Gitea version (or commit ref): 1.8.3 ## Description If I do a `cat ~/.ssh/id_rsa.pub` and copy paste it in Gitea to the textarea to add a new deploy key, I get the error "Can not verify your SSH key: extractTypeFromBase64Key: invalid key format: illegal base64 data at input byte 168" If I remove the line break in the middle, it works. It seems that Gitea doesn't handle line returns inside keys.

GiteaMirror added the issue/needs-feedback label 2025-11-02 05:19:24 -06:00

GiteaMirror closed this issue

2025-11-02 05:19:24 -06:00

GiteaMirror commented

2025-11-02 05:19:25 -06:00

@silverwind commented on GitHub (Jul 17, 2019):

SSH Keys have no linebreaks in the middle, it's probably your terminal erronously adding them. Does adding the same faulty key on GitHub work, btw?

It may be possible that we can prevent such errors by stripping any \r?\n sequences from the added key on save because those should never appear in a key afaik.

@silverwind commented on GitHub (Jul 17, 2019): SSH Keys have no linebreaks in the middle, it's probably your terminal erronously adding them. Does adding the same faulty key on GitHub work, btw? It may be possible that we can prevent such errors by stripping any `\r?\n` sequences from the added key on save because those should never appear in a key afaik.

GiteaMirror commented

2025-11-02 05:19:26 -06:00

@bohwaz commented on GitHub (Jul 18, 2019):

SSH Keys have no linebreaks in the middle, it's probably your terminal erronously adding them. Does adding the same faulty key on GitHub work, btw?

Yes it works on github and gitlab.

It may be possible that we can prevent such errors by stripping any \r?\n sequences from the added key on save because those should never appear in a key afaik.

Would be a good solution :)

@bohwaz commented on GitHub (Jul 18, 2019): > SSH Keys have no linebreaks in the middle, it's probably your terminal erronously adding them. Does adding the same faulty key on GitHub work, btw? Yes it works on github and gitlab. > It may be possible that we can prevent such errors by stripping any `\r?\n` sequences from the added key on save because those should never appear in a key afaik. Would be a good solution :)

GiteaMirror commented

2025-11-02 05:19:26 -06:00

@bohwaz commented on GitHub (Aug 7, 2019):

Great, thank you :)

@bohwaz commented on GitHub (Aug 7, 2019): Great, thank you :)

GiteaMirror referenced this issue

2025-11-02 12:24:16 -06:00

[PR #3610] [MERGED] Changelog for release 1.4.0-rc2 #17014

Sign in to join this conversation.