Skip to content
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.

bw cli 2024.4.0 appears broken (again) #195

Open
luckman212 opened this issue May 11, 2024 · 3 comments
Open

bw cli 2024.4.0 appears broken (again) #195

luckman212 opened this issue May 11, 2024 · 3 comments

Comments

@luckman212
Copy link
Collaborator

reminds me of #186

I just filed an issue...

bitwarden/clients#9142

Is everyone else having problems too?

@rpop0
Copy link

rpop0 commented May 20, 2024

Yeah it's broken, I can't use the workflow for a couple of months. Seems like the project is abandoned.

@luckman212
Copy link
Collaborator Author

Sad to say but I believe that yes it's time to throw in the towel on Bitwarden CLI. They just don't seem to care about it, and it's been broken in various ways for months. Even when it is working, it's too slow (for me) to be very useful. And then you start getting into leaving cached versions of your vault lying around on the disk which probably isn't a great idea security-wise.

I switched to 1Password last week and honestly I can't believe how much better it is, literally in EVERY way. Only wish I had done it sooner, as I've lost days of my life to debugging and working around silly Bitwarden issues.

@blacs30
Copy link
Owner

blacs30 commented May 21, 2024

I am testing currently this workflow, which uses the bitwarden cli only but has all important features and more.
https://github.com/ajrosen/Bitwarden-Accelerator

I didn't make it yet official but I tend to recommend users to use that workflow.
Right now the Masterpassword is visible in cleartext in debug mode - but I hope that will be changed.

1Password is of course very nice and more powerful, specially their global autofill.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants