docker-credential-helpers VS lastpass-cli

Docker supports a credential-helper module[0], which supports 4 different backends for fetching the docker registry credentials: osxkeychain, pass, wincred, and secretservice.

pass lets you use GPG-smartcards, and many of those (such as Yubikeys) will let you enforce touch-policies for signing/encruption.

As a combination of both these however, I must touch my Yubikey every time I pull a new docker image.

Another cool use-case is that I use the terraform-pass-provider to save secrets for my personal terraform project.

[0]: https://github.com/docker/docker-credential-helpers

# Finds the latest version $ wincred_version=$(curl -fsSL -o /dev/null -w "%{url_effective}" https://github.com/docker/docker-credential-helpers/releases/latest) # Downloads and extracts the .exe $ sudo curl -fL \ "https://github.com/docker/docker-credential-helpers/releases/download/${wincred_version}/docker-credential-wincred-${wincred_version}-$(dpkg --print-architecture).zip" | zcat | sudo tee /usr/local/bin/docker-credential-wincred.exe >/dev/null # Assigns execution permission to it $ sudo chmod +x /usr/local/bin/docker-credential-wincred.exe

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