Jump to content

Andy Rosen

Member
  • Posts

    53
  • Joined

  • Last visited

Recent Profile Visitors

486 profile views

Andy Rosen's Achievements

Member

Member (4/5)

1

Reputation

  1. DO NOT UPGRADE BITWARDEN-CLI PAST 2024.6.0 A bug was introduced in version 2024.6.1 of the Bitwarden CLI that prevents you from unlocking your vault. Version 2024.7.0, released yesterday, does not fix it. Homebrew currently has 2024.6.1. https://github.com/bitwarden/clients/issues/9919
  2. Hi @jk-alfred, thanks for using the workflow! If I understand the first request (1.a and 1.b), you'd like to change the Command modifier to open an item's URL instead of copying its Notes field? I'm reluctant to change modifier settings, as there may be people who have gotten used to the current ones. I can offer to add a new one. For 1.c, in my testing, opening an item in the web vault requires me to login, even if I'm already logged in. This is true at least for Firefox and Safari. That's why I've left it out. I can add ItemId, Type, and RevisionDate to Show all fields and Navigate item in Alfred. And I like the idea of a Return to Previous Page line; I would probably use that myself. For the last one, I don't think there's enough room to show all the buttons. The subtitle/tooltip does change when you hold a modifier key down.
  3. Version 4.2.0 Download link Add support for Firefox Developer Edition
  4. Version 4.1.2 Download link Hide password and MFA even from debug messages Always sync vault immediately after unlocking
  5. I totally understand. I switched from LastPass to Bitwarden for similar reasons. It seemed development had stopped, especially the CLI, and it was too expensive to live with its flaws. I don't quite remember why I originally settled on LastPass over 1Pasword; too long ago.
  6. Does the desktop app and/or browser extension perform better? I have about 600 items in my vault. My M1 Air takes about 0.3 seconds (curl) and 3.2 seconds (bw list). If rebooting doesn't help you might want to open an issue with Bitwarden on GitHub here.
  7. Version 4.1.1 Download link Fix launch agent label
  8. @luckman212 For your second point, it is confusing but the workflow enables/disables the launch agent by loading or unloading it. The only way I know of to check is by running launchctl list. If you see - 0 org.mlfs.corp.bw in the output, the launch agent is loaded. If you don't, it's not. But wait! There's a bug! The launch agent is incorrectly labeled BUNDLEID, not org.mlfs.corp.bw. I'll publish a fix shorly. One thing to keep in mind is that configuring the workflow is not enough to affect changes. You need to do a search for any changes to be saved.
  9. Hello @luckman212! The workflow looks in a few specific directories for the bw executable, in this order: /usr/local/bin /opt/homebrew/bin /opt/local/bin /usr/local/Cellar/bitwarden-cli/*/bin /opt/homebrew/Cellar/bitwarden-cli/*/bin If it finds one it creates a symbolic link to it in the workflow's cache directory. You can work around this by creating the symlink manually: ln -s ~/.n/bin/bw ~/Library/Caches/com.runningwithcrayons.Alfred/Workflow\ Data/org.mlfs.corp.bw/bw You may need to do the same for jq if it's not installed in one of the directories listed above.
  10. Version 4.1.0 Download link Add support for Arc
  11. Version 4.0.0 Download link View an item's fields directly within the workflow. Use either command+option or as a Universal Action. Select the field to copy its value to the clipboard. Thanks to @blacs30 for describing this use case
  12. You are correct, this workflow is based on bw serve, and I agree that its security model is...interesting. But I feel it's the best option for an Alfred workflow. The CLI itself is unacceptably slow without caching the results. On my MacBook Air (M1 2020) it takes at least 3 seconds to execute bw list items. $ time bw list items > /dev/null 1.063u 0.181s 0:03.16t 39.2% Even bw get item <id> takes 3 seconds. So there has to be something that keeps it all in RAM. Doing that myself might have better security than bw serve if properly implemented. I prefer not to take on that responsibility. And I'm not even sure security could be improved that much. I'm not aware of any macOS primitives that could address the biggest weakness (the TCP socket open to any user/process). I do wish bw serve could at least implement Master password re-prompt.
  13. There is also LastPass Accelerator. Packal: https://www.packal.org/workflow/lastpass-accelerator Github: https://github.com/ajrosen/Alfred/tree/master/LastPass Accelerator I have switched from LastPass to Bitwarden for my own passwords, so I haven't updated LastPass Accelerator in a while. But if there's interest, I'd be happy to get back to it. I could bring in some features of Bitwarden Accelerator that I think are really cool (if I do say so myself 😉).
  14. Version 3.2.0 Download link Add support for Ghost Browser
×
×
  • Create New...