Open fionnb opened 2 years ago
@fionnb is it possible to run with --logLevel=debug
, it might help to understand where it fails.
im abit late but here is the debug output
running on Arch (EndeavorOS)
edit: ssh-manager v1.8.6
ok so anyone having problems you need to run
bw unlock
just copy and run the
export BW_SESSION="SuperSecretKey"
then you can use ssh-manager without any problems hopefully
maybe could bee a good idea to check if the user has BW unlocked when running ssh-manager
Describe the bug Adding a key via bw provider reports success, even though the key is not stored.
To Reproduce Steps to reproduce the behavior:
bw lock
ssh-manager add --provider bw --name test123 --private-key bla --public-key bla.pub
time="xx-yy-2022 22:22:22" level=info msg="Manager Keys saved for test123."
Expected behavior An error message, stating that the key could not be added.
Environment:
ssh-manager version
): ssh-manager v1.1.0