failed to parse message from agent: EOF while parsing a value at line 1 column 0

[nkfilis]

With any rbw command that seems to interact with the backend, I get the above error, for example rbw login:

rbw login: failed to parse message from agent: EOF while parsing a value at line 1 column 0

Is there a way to get more verbose output?
My rbw config show:

{
  "email": "myusername@bitwarden.com",
  "base_url": null,
  "identity_url": null,
  "lock_timeout": 3600
}

I'm running on 0.5.2

[doy]

you should be able to find agent logs at ~/.local/share/rbw/ - they may have more information?

[doy]

i'm going to close this out now because i don't really have enough information to look into this any further, but feel free to reopen this with additional information if it continues to happen.

[minego]

I am running into this issue as well. Unfortunately that directory doesn't appear to exist on my system. Is the path different on macs?

[minego]

I found the logs in ~/Library/Application Support/rbw and here is the relevant portion:

pinentry-curses: no LC_CTYPE known - assuming UTF-8
thread 'tokio-runtime-worker' panicked at 'Client::new(): reqwest::Error { kind: Builder, source: UnsupportedCriticalExtension }', /Users/brew/Library/Caches/Homebrew/cargo_cache/registry/src/github.com-1ecc6299db9ec823/reqwest-0.11.9/src/async_impl/client.rs:1263:38

[minego]

As far as I can tell a library that rbw uses is unhappy with either my cert or something in the cert chain? I don't see why. My cert comes from Let's Encrypt.

[doy]

huh, fascinating. yeah, it is disliking something about your tls certificate. would it be possible for me to see the certificate you are using?

[minego]

Sure, it is on https://bitwarden.minego.net/

[minego]

I should point out that this cert is accepted by rbw on my Linux boxes, but fails on my macOS box. I've done a brew update, and am running the latest OS and all updates from Apple.

[minego]

Were you able to test with my cert?

[languitar]

This seems to be related to parsing the trusted certificates installed on the system with rustls-native-certs: rustls/rustls-native-certs#15 Some certificate in the local trust chain prevents building up the whole trust store. The linked issue contains a workaround/solution that would need to be implemented here -- if I understand it correctly -- to make this work again.