Hi!
I currently have the problem, or rather the minor inconvenience, that the ssh socket is not populated on startup.
And when trying to access any ssh key I get rejected. This is especially annoying when writing commit messages and getting reject because the signing key was not found. Thus having to first to start the agent, using rbw unlock and then re-write the commit message.
It would be nice to have a sub command that starts the agent, without performing any other operations.
This way you could start the agent on startup and the user would be prompted (using pinentry) to unlock the vault, without having to explicitly start/unlock the agent using rbw unlock.
Hi!
I currently have the problem, or rather the minor inconvenience, that the ssh socket is not populated on startup.
And when trying to access any ssh key I get rejected. This is especially annoying when writing commit messages and getting reject because the signing key was not found. Thus having to first to start the agent, using
rbw unlockand then re-write the commit message.It would be nice to have a sub command that starts the agent, without performing any other operations.
This way you could start the agent on startup and the user would be prompted (using pinentry) to unlock the vault, without having to explicitly start/unlock the agent using
rbw unlock.