bytecodealliance
`warg key new` fails opening platform secure storage
@fibonacci1729
error: failed to set signing key with name `default` of registry `http://localhost:8090`: Platform secure storage failure: zbus error: org.freedesktop.Secret.Error.IsLocked: Cannot create an item in a locked collection
After some investigation I believe this is related to running in a headless environment. Since that is likely to be somewhat common for this tool I think we'll need an alternative way to store keys.
Hi @lann
Any updates on this end?
Today, I installed warg, and when I attempt to set the key for my local repository at 127.0.0.1:8090, I encounter the same error. Subsequently, I installed gnome-keyring using the command:
sudo apt install gnome-keyring
After installing gnome-keyring, I re-executed the warg command, and now I am encountering the following error:
warg key new 127.0.0.1:8090
error: failed to set signing key with name `default` of registry `https://127.0.0.1:8090/`: Couldn't access platform secure storage: SS error: result not returned from SS API
Btw, I'm running warg in a headless environment and I have installed warg server In-memory storage following guideline https://github.com/bytecodealliance/registry/blob/main/crates/server/README.md
Take a look at https://github.com/bytecodealliance/registry/discussions/237 for some relevant discussion about warg development. We are taking another look at private key management for publishers since it still such a pain.