lastpass-cli VS pass-import

The other difficulty is it appears there is little-to-no support for API/automation:

https://github.com/lastpass/lastpass-cli/issues/602

https://github.com/lastpass/lastpass-cli/issues/624

https://github.com/lastpass/lastpass-cli/issues/604

...their CLI tool is de-facto deprecated (unsupported) and has several unreliability issues (ie: `lpass ls/userls ...` reports differing amounts of values depending on when a user was added to the folder or not). Basically `lpass ls ... | xargs -n1 ...` cannot be trusted, and you can only get an accurate list of passwords (or users) from the actual GUI.

It makes automation, auditing, reporting, near impossible.

When saving the CSV, do not copy-paste the content of the HTML manually, instead use the popup to download the file that LastPass provides. You might need to allow popups for LastPass extension the first time you perform the export, then perform another one to get the popup.

# 2. Export attachments

Use lastpass-cli to export attachments. A script is provided in version 1.3.4: https://github.com/lastpass/lastpass-cli/blob/v1.3.4/contrib...

https://github.com/lastpass/lastpass-cli/blob/master/contrib/lpass-att-export.sh helped me batch-export my attachments.

You can see the source code for a lastpass client here.

(define-module (lastpass-cli) #:use-module (guix utils) #:use-module (guix packages) #:use-module (guix download) #:use-module (guix build-system cmake) #:use-module (guix licenses) #:use-module (gnu packages bash) #:use-module (gnu packages curl) #:use-module (gnu packages xml) #:use-module (gnu packages gnupg) #:use-module (gnu packages pkg-config) #:use-module (gnu packages tls) ) (define-public lastpass-cli (package (name "lastpass-cli") (version "1.3.3") (source (origin (method url-fetch) (uri (string-append "https://github.com/lastpass/lastpass-cli/releases/download/v" version "/lastpass-cli-" version ".tar.gz")) (sha256 (base32 "06v7d1khk5ylhmf1giqpgq97gsn6mnqhg0637gnryv704wb5jkxr")))) (build-system cmake-build-system) (arguments ;; disable tests? '(#:tests? #f)) (native-inputs (list pkg-config)) (inputs (list bash openssl curl libxml2 pinentry)) (synopsis "Command line interface to LastPass.com") (description "") (home-page "https://github.com/lastpass/lastpass-cli") (license gpl2))) lastpass-cli

Their CLI seems to support showing attachments: https://github.com/lastpass/lastpass-cli/blob/8767b5e53192ad...

FYI for those interested in CLI password management, there is a pretty good CLI for LastPass called lpass that even supports your Yubikeys.

https://github.com/lastpass/lastpass-cli

> I always tell these people to just sign up for a password manager and they always resist and say no. I must be missing something obvious.

Maybe they don't want to be relying on a random third-party for all their passwords?

Rather than getting them to sign up for a password manager, what about getting them to install a password manager? I use https://www.passwordstore.org/ - it encrypts your passwords with GPG, and shares the storage via a Git repository for synchronisation between different machines.

That way you can delegate the password handling to another program, e.g. a password manager like pass(1) (https://www.passwordstore.org/) or some interactive graphical prompt.

I want to move to something compatible with https://www.passwordstore.org/ - an open standard for keeping your passwords in a folder encrypted with OpenPGP.

The problem is that I'm nervous to give an unknown Android app and browser plugin total control of my passwords and access to my github account when I don't have time to review it's code properly. I have a bit more trust ing the command line tools, but I'd like to be sure that more people are looking at the code before I trust my life to it.

> Create a system or pattern based on url or brand and mentally hash it into a password.

Doesn't sound very secure. Also when you realize that you anyway have to trust cryptography, I believe it starts making a lot of sense to have an actual cryptographic key and encrypt it with one good random password you learn by heart.

I use pass https://www.passwordstore.org/, which encrypts my passwords with my GPG key, which comes from my Yubikey, which I unlock with a password. That means that I only need to remember one password, and it feels a lot more secure than your pattern based on url or brand.

i use pass and keep my database on a local git repo. it encrypts your passwords with gpg and is a really simple command line program

If you want portability and simplicity, there's a project called simply pass that uses standard *nix utilities (and git, I believe) to manage passwords from CLI.

0. Pass is just text files encrypted with gpg. I needed just one password on one work computer, where I had my gpg key, but not all my passwords. Decrypted the file and that was it.

1. There are plugins and web clients: https://www.passwordstore.org/#extensions

I've been incredibly happy with https://www.passwordstore.org/ for years. The data store is a file hierarchy, with the files themselves encrypted with GPG. Sync is via git. TOTP support with a plugin.