From nicolai at dagestad.fr Mon Aug 17 15:30:24 2026 From: nicolai at dagestad.fr (Nicolai Dagestad) Date: Mon, 17 Aug 2026 17:30:24 +0200 Subject: [PATCH] Fix extensions install dir In-Reply-To: <87cxwbj8l0.fsf@nyarlathotep> References: <87cxwbj8l0.fsf@nyarlathotep> Message-ID: On Sat Jul 25, 2026 at 7:13 PM CEST, jman wrote: > > Hi, > > by reading the man page it looks like that the desired install dir for the extensions is > "PASSWORD_STORE_DIR/.extensions". > For this reason I think the Makefile is wrong when creating "PASSWORD_STORE_DIR/extensions", it > should create that directory according to what the manual says, right? > > Opinions? > > Thanks Hi, It looks to me like the Makefile doesn't create "PASSWORD_STORE_DIR/extensions" but "$(DESTDIR)$(LIBDIR)/password-store/extensions". The difference between the 2 is that the first one is in your password store with all you passwords - in which case having it in a hidden directory is nices - but the second one is installed on you system - defaulting to /usr/lib - and there it doesn't really make sens to have it be a hidden directory. From nshephard at protonmail.com Tue Aug 18 06:32:27 2026 From: nshephard at protonmail.com (Neil) Date: Tue, 18 Aug 2026 06:32:27 +0000 Subject: Tag for newer password-store.el Message-ID: Hi, I've been using pass + password-store.el for a number of years and find them both to be brilliant, thank you for writing and maintaining such excellent software. Recently I noticed whilst trying to fix a minor issue with versions with the new MELPA snapshots (see pull request at https://github.com/melpa/melpa/pull/10127) that the stable version in MELPA is 1.7.4 (https://stable.melpa.org/#/password-store) but the version noted in the last commit to touch password-store.el (https://git.zx2c4.com/password-store/commit/?id=3ca13cd8882cae4083c1c478858adbf2e82dd037) bumped the version to 2.3.3. As noted in the MELPA PR (https://github.com/melpa/melpa/pull/10127#issuecomment-5304364156) there is no 2.3.3 tag. Is it possible to tag the above commit with 2.3.3 so the version noted on MELPA Stable and the newer MELPA Snapshots (https://snapshot.melpa.org/#/password-store) reflects the version that is actually being pulled in? I don't think its appropriate for me to add the tag myself hence posting and asking. Thanks, Neil -- Ignorance more frequently begets confidence than does knowledge?- Charles Darwin We do not inherit the earth from our ancestors. We borrow it from our children.?-? Christine Gebeneter PGP Public :?0x700172212EF5818B -------------- next part -------------- A non-text attachment was scrubbed... Name: publickey - nshephard at protonmail.com - 0x1078D130.asc Type: application/pgp-keys Size: 600 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 343 bytes Desc: OpenPGP digital signature URL: From higuita at GMX.net Tue Aug 25 18:32:41 2026 From: higuita at GMX.net (higuita) Date: Tue, 25 Aug 2026 19:32:41 +0100 Subject: Export and import all store data In-Reply-To: References: Message-ID: <20260825193241.16e32d6b@couracado.motaleite.net> Hi > This is a follow-up to the continued ?There is no assurance this key > belongs to the named user? issue I?m encountering with `pass`: > > https://lists.zx2c4.com/pipermail/password-store/2026-April/004974.html > https://marc.info/?l=gnupg-users&m=157167920418502 I do see this error many times and i think i have a method to fix this. So my setup is that I use pass in my company and we have several admins in the password store .gpgid, that is loaded in to a central git so everyone can clone. Every time i need to add a new admin, i need to add his gpg key ID to the .gpg-id, and import his key. This is when the error "There is no assurance this key belongs to the named user? To fix, i need to edit that key, sign it, run gpg --check-trustdb (i actually think this is not really needed, but always good to run every few months) and only after all these steps, i can reencrypt all store to include the new key with the error fixed. I build a Makefile (see below) to help and place it in the ~/.password-store and then i enter that dir and run "make". it will return a short help. Of course, you need "make" installed Run make import-and-sign to check all .gpg-id and import those keys and try to sign them. If your own key isn't working well (like it was imported), edit your own key, trust and choose "5 = I trust ultimatel" and save. This will make your own private key as a fully trusted and working key. Hope this helps higuita --- .DEFAULT_GOAL := help GPG = $(shell command -v gpg2 || command -v gpg) ifeq ($(GPG),) $(error "gpg2 or gpg not found in PATH") endif GPG_MAJOR_VERSION = $(shell $(GPG) --version | awk 'NR==1 { split($$4,version,"."); print version[2]}') .PHONY: help help: @grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}' @echo "\n Example: cd ~/.password-store/internal; make -f ~/.password-store/Makefile list-keys \n" .PHONY: import-and-sign import-and-sign: ## Import in GPG all keys from the list of allowed keys $(foreach var,$(shell find . -name .gpg-id | xargs cat | sort | uniq), \ ( \ $(GPG) --list-public-key $(var) || \ $(GPG) --keyserver hkp://keyserver.ubuntu.com --search-keys $(var); \ ) && \ $(GPG) --sign-key $(var); \ ) .PHONY: list-keys list-keys: ## List all the keys in the store with ID and names @for key in $$( find . -name .gpg-id | xargs cat | sort | uniq ); do \ printf "$${key}: "; \ if [ "$(GPG_MAJOR_VERSION)" = "2" ]; then \ $(GPG) --list-keys --with-colons $$key 2> /dev/null | awk -F: '/^uid/ {found = 1; print $$10; exit} END {if (found != 1) {print "*** not found in local keychain ***"}}'; \ else \ $(GPG) --list-keys --with-colons $$key 2> /dev/null | awk -F: '/^pub/ {found = 1; print $$10} END {if (found != 1) {print "*** not found in local keychain ***"}}'; \ fi;\ done .PHONY: check-pass-store check-pass-store: ## Check if you can read all the keys @for i in $$(find . -name '*.gpg' | sed 's/\.gpg$$//;s/^.\///'); do \ echo "Checking $$i"; \ PASSWORD_STORE_DIR=$$(pwd) pass $$i > /dev/null || exit 1; \ done @echo "OK: All password entries are readable" .PHONY: reencrypt reencrypt: ## Reencrypt for the currrent user list @for i in $$(find . -name '.gpg-id' | sed 's,^\./.gpg-id,.,g; s,^\./,,g; s,/\.gpg-id,,g' ); do \ echo "Applying $$i"; \ PASSWORD_STORE_DIR=$$(pwd) pass init --path=$$i $$(cat $$i/.gpg-id ) > /dev/null || exit 1; \ done @echo "OK: All password entries were reencrypted" -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946