[GH-ISSUE #218] ConfigQemu.Sshkeys are not properly URL encoded by ConfigQemu.UpdateConfig() #48

Closed
opened 2026-02-28 00:40:20 +03:00 by kerem · 0 comments
Owner

Originally created by @nikitawootten on GitHub (Nov 29, 2022).
Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/218

This issue shows itself when attempting to update a resource with an SSH key that has : in a comment, which is common in workflows involving smartcards and GPG-agent. Users of this package attempting to add an offending key (including through downstream projects such as in this case in the terraform proxmox provider will get an error.

For example, one of my keys ends like this:

ssh-rsa AAAA...== cardno:18 228 342

This URL encoding currently happens in ConfigQemu.UpdateConfig() on line 456.

Originally created by @nikitawootten on GitHub (Nov 29, 2022). Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/218 This issue shows itself when attempting to update a resource with an SSH key that has `:` in a comment, which is common in workflows involving smartcards and GPG-agent. Users of this package attempting to add an offending key (including through downstream projects such as in [this case in the terraform proxmox provider](https://github.com/Telmate/terraform-provider-proxmox/issues/133) will get an error. For example, one of my keys ends like this: ``` ssh-rsa AAAA...== cardno:18 228 342 ``` This URL encoding currently happens in `ConfigQemu.UpdateConfig()` on [line 456](https://github.com/Telmate/proxmox-api-go/blob/73720ef02c2e5c913fe0633a0e747a43fc356aad/proxmox/config_qemu.go#L456).
kerem closed this issue 2026-02-28 00:40:20 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
starred/proxmox-api-go#48
No description provided.