[GH-ISSUE #6068] Can't add an existing ssh-key to vault-varden #2329

New issue

Closed

opened 2026-03-03 02:17:15 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 02:17:15 +03:00

Owner

Originally created by @Timo-1979 on GitHub (Jul 16, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6068

Steps to reproduce:

Create an entry of type ssh-key

Actual Behaviour:

all Fields in Section "SSH key" are:

pre-filled with a newly generated ssh-key
disabled and not option to edit

Expected Behaviour:
all Fields in Section "SSH key" are:

OK - pre-filled with a newly generated ssh-key
at least the field private-key is editable
If the web-ui could extract the public-key and fingerprint from the private-key the fields "public-key" and "Fingerprint" are show the correct value - otherwise the field become blank

Originally created by @Timo-1979 on GitHub (Jul 16, 2025). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6068 Steps to reproduce: - Create an entry of type ssh-key Actual Behaviour: all Fields in Section "SSH key" are: - pre-filled with a newly generated ssh-key - disabled and not option to edit Expected Behaviour: all Fields in Section "SSH key" are: - OK - pre-filled with a newly generated ssh-key - at least the field private-key is editable - If the web-ui could extract the public-key and fingerprint from the private-key the fields "public-key" and "Fingerprint" are show the correct value - otherwise the field become blank