You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a GPG key is created via keykeeper, the name can contain a /, however when querying the GPG key via /v1/keys/<name>/public-key, keykeeper fails to return any key despite proper URL encoding.
Reproduction Steps
create a GPG key with a / in the name
POST http://localhost:46002/v1/generate-key
{
"name": "Rocky Linux 10 - Beta Key V1/2024",
"email": "[email protected]",
"fingerprint": "1e377f6e43ae776433685789ad4f9579597db479"
}
query the gpg key
GET http://localhost:46002/v1/keys/Rocky Linux 10 - Beta Key V1%2F2024/public-key
n.b. it makes no difference if the spaces are urlencoded or not
Expected Behavior
Keykeeper API would return the GPG key for this named key
Version and Build Information
main
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe The Bug
When a GPG key is created via keykeeper, the name can contain a
/
, however when querying the GPG key via/v1/keys/<name>/public-key
, keykeeper fails to return any key despite proper URL encoding.Reproduction Steps
/
in the namen.b. it makes no difference if the spaces are urlencoded or not
Expected Behavior
Keykeeper API would return the GPG key for this named key
Version and Build Information
main
Additional context
No response
The text was updated successfully, but these errors were encountered: