Codeberg/Community
62
387
Fork
You've already forked Community
12

cannot update SSH key #2777

Open
opened 2026年06月19日 15:14:36 +02:00 by m4r35n357 · 3 comments

Comment

The data I upload is displayed incorrectly. I cannot get my key data to appear on the UI. It seems to hold on to previous data. The data displayed after "save" is NOT what I pasted!

Sorry I cannot be more specific - it is confusing and I have no idea what to do now!

I am posting here so you know it is me and not an impostor!

BTW I am not a newbie, so please don't assume that.

### Comment The data I upload is displayed incorrectly. I cannot get my key data to appear on the UI. It seems to hold on to previous data. The data displayed after "save" is NOT what I pasted! Sorry I cannot be more specific - it is confusing and I have no idea what to do now! I am posting here so you know it is me and not an impostor! BTW I am not a newbie, so please don't assume that.

Well, I have just uploaded a new key and it works, but the UI is showing incorrect contents (I uploaded an ed25519 and it is showing as sha256 (with incorrect contents). Perhaps it is displaying an old key from a defunct computer so I cannot check!

Well, I have just uploaded a new key and it works, but the UI is showing incorrect contents (I uploaded an ed25519 and it is showing as sha256 (with incorrect contents). Perhaps it is displaying an old key from a defunct computer so I cannot check!

@m4r35n357 wrote in #2777 (comment):

(I uploaded an ed25519 and it is showing as sha256 (with incorrect contents).

Sorry, but this is correct. This displays the SHA256 fingerprint of the SSH key. You can generate this locally via $ ssh-keygen -lf /path/to/ssh/key and this should match that fingerprint. It's unpractical to show the key contents with keys like RSA that have a long public key.

@m4r35n357 wrote in https://codeberg.org/Codeberg/Community/issues/2777#issuecomment-17886194: > (I uploaded an ed25519 and it is showing as sha256 (with incorrect contents). Sorry, but this is correct. This displays the SHA256 fingerprint of the SSH key. You can generate this locally via `$ ssh-keygen -lf /path/to/ssh/key` and this should match that fingerprint. It's unpractical to show the key contents with keys like RSA that have a long public key.

OK, your explanation makes sense, but that was a surprising outcome, to me at any rate. How about a note to that effect (on the page) when showing your "local" fingerprint?

OK, your explanation makes sense, but that was a surprising outcome, to me at any rate. How about a note to that effect (on the page) when showing your "local" fingerprint?
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
 Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
 Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
 This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2777
Reference in a new issue
Codeberg/Community
No description provided.
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?