1Password: Standalone / Local Vault Option Gone?

Re:1Password: Standalone / Local Vault Option Gone? by txcwpalpha on Friday July 12, 2019 @04:09AM (#20419113)

Did you actually try using the CLI tool, or did you only read the documentation? The documentation isn't super clear, but in actual usage your password (nor your email) doesn't get entered into shell history or otherwise.

You can pass your email and password as arguments to the "bw login [email] [password]" command, which will put them into your history, but the default way of typing "bw login" will then prompt you for them both, masking your password just like any other CLI tool does.

[ Parent | on HN ]

Re:1Password: Standalone / Local Vault Option Gone? by stouset on Friday July 12, 2019 @03:44PM (#20423778)

If if you can do this, the fact that the documentation encourages you to do otherwise is extremely worrisome. Securely-written tools shouldn't even allow you to do this in the first place, much less promote it.

https://help.bitwarden.com/article/cli/

[ Parent | on HN ]

Re:1Password: Standalone / Local Vault Option Gone? by krmbzds on Saturday July 13, 2019 @02:12AM (#20426747)

I don't think it's extremely worrisome. The arguments are in brackets a.k.a. they are optional. If a user doesn't know that they probably shouldn't be using the command line tool in the first place. Besides, if you run help on the cli tool the first example it suggests is "bw login" (without the arguments).

[ Parent | on HN ]