Package Details: pass-import 3.1-2

Git Clone URL: (read-only, click to copy)
Package Base: pass-import
Description: A pass extension for importing data from most of the existing password manager.
Upstream URL:
Keywords: import pass pass-extension
Licenses: GPL3
Submitter: roddhjav
Maintainer: roddhjav
Last Packager: roddhjav
Votes: 25
Popularity: 0.014913
First Submitted: 2017-01-09 17:56
Last Updated: 2020-12-10 17:46

Dependencies (9)

Required by (0)

Sources (2)

Pinned Comments

roddhjav commented on 2018-01-06 18:17

To install the package first import my PGP key:

gpg --recv-keys 06A26D531D56C42D66805049C5469996F0DF68EC

Alternatively add keyserver-options auto-key-retrieve to your ~/.gnupg/gpg.conf.

This key can also be found on

Latest Comments

1 2 Next › Last »

chovy commented on 2021-01-05 06:21

none of this works

nallekarhu commented on 2020-10-25 19:19

pass-import fails after upgrading to python-pykeepass 3.2.1-2 Downgrading to python-pykeepass 3.2.0-1 solved it for me

EDIT: no longer necessary after upgrading to pass-import 3.1-1

DAMO238 commented on 2020-09-29 18:00

It seems that the keys have not been distributed between keyservers very well, I had to get them from the mit keyserver (which is slow and unreliable). Just add the following to your gpg configuration file:

keyserver hkps://

roddhjav commented on 2020-04-16 17:54

@babbarc This is not related to the package but to your pacman configuration. It is looking for the signature of the package pass-import-2.6-2-any you made yourself. Either you need to disable LocalFileSigLevel signature checking in pacman.conf or you need to ensure makepkg (or your aur helper) signed the package with your GPG key.

babbarc commented on 2020-04-16 17:31

Getting the below error while installing

error: 'path/to/pass-import/pass-import-2.6-2-any.pkg.tar.xz': package missing required signature

PS: I have the required signature

roddhjav commented on 2020-03-29 12:49

@stratosgear You might want to configure the keyserver in ~/.gnupg/gpg.conf with one of those:

keyserver hkps://
keyserver hkps://

Also some networks (university for instance) block the hkps protocol.

stratosgear commented on 2020-03-29 12:41

Which I fixed by manually downloading your Code Signing Key from your website at and then doing a 'gpg --import 0xc5469996f0df68ec.asc`.

BTW, regarding my previous message, installing with yay/pacman also causes the same error.

No idea why you key is not automatically downloaded with --recv-keys

stratosgear commented on 2020-03-29 12:24

Still I cannot import your keys:

gpg --recv-keys 06A26D531D56C42D66805049C5469996F0DF68EC                             
gpg: enabled debug flags: memstat
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keydb: handles=0 locks=0 parse=0 get=0
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=0 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=0 cached=0 good=0 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks

roddhjav commented on 2019-06-09 20:30

@nallekarhu That's is small (now fixed in upstream) bug. Meanwhile you can import your passwords with the keepass importer: pass import keepass file.kdbx it calls the same function but without this bug.

nallekarhu commented on 2019-06-09 20:24

Trying to import from keepassxc:

pass import keepassxc file.kdbx


Password for <_io.TextIOWrapper name='file.kdbx' mode='r' encoding='utf-8'>: