rbw 1.9.0 not working with latest vaultwarden about rbw HOT 6 OPEN

can you provide me with the vaultwarden version you're using, and the output of rbw config show? i'm currently successfully using rbw 1.9.0 with the latest vaultwarden (1.30.5) without any issues, so i'll need some more information to dig further into this.

from rbw.

i've now downloaded 1.10 from rbw.
diffrent error same outcome
I'm using Version 2024.1.2 of vaultwarden

when i've configured base_url and email
rbw login or rbw register lead to error:
rbw register: failed to run rbw-agent: No such file or directory (os error 2)

rbw and rbw-agent are in the same directory

rbw config show

{
"email": "[email protected]",
"base_url": "https://some.url.com/",
"identity_url": null,
"notifications_url": null,
"lock_timeout": 3600,
"sync_interval": 3600,
"pinentry": "pinentry",
"client_cert_path": null
}

from rbw.

@mamema is rbw-agent in $PATH? That error might also mean that your rbw-agent is a broken symlink

from rbw.

ok, copying the rbw and rbw-agent into /usr/bin lead to a normal login, but every command executed
eg: rbw ls
lead to:

rbw list: TODO

vaultwarden then sent an email with the content "Someone attempted to login your account with the correct master password, but did not provide the correct token or action required to complete the two-step login process within 3 minutes"

this got solved with rbw register. then. vaultwarden just stated a new login, but the above statement remains.
i got only

rbw list TODO

back

from rbw.

I had the same / similar issue. Master key was 100% correct. Still had to enter it 3 times, always returning an error. I think it might have to do with the KDF iterations? I set them from 100000 to 1000000. I was not able to log into vaultwarden. I was able to fix it by doing the following:

rbw lock
rbw purge
rbw login
rbw sync
rbw list

I guess only rbw pruge is needed. Just posted all the commands I executed until it worked again.

from rbw.

I'm having a problem similar to this, but it corrupts my terminal such that most keyboard inputs are lost somewhere. It won't register simple things like ctrl-c or ctrl-d after failing the password input. If i continue to mash the key, I get something like 1 input per 12 key presses. If i rbw login and then ctrl-c immediately, my terminal is broken.

I switched to pinentry-curses from pinentry-tty and the dropped input problem disappears, but the password still always fails.

from rbw.