Sorry, I just noticed that my keys were created using DSA (sign only), which apparently it's not useful for encrypting. I was using option 3:
Please select what kind of key you want: (1) RSA and RSA (default) (2) DSA and Elgamal (3) DSA (sign only) (4) RSA (sign only) I created a key using option 2 and it worked fine. Sorry for the false alarm/noise! BTW, what about adding key creation to the docs? Regards, Santiago On Fri, Apr 1, 2016 at 5:04 PM, Santiago Borrazás <[email protected]> wrote: > Hello there, > > I created several DSA keys and none of them were working. I always got > "gpg: 2048D/19XXXD3: skipped: No public key". > > After trial and error I discovered that pass *would only accept RSA keys*. > > I tried adding these DSA keys by their ids, like 'pass init 11223344'. > Also, as I found in a blog post, I tried adding the key using the email, > which unfortunately neither worked ('pass init [email protected]'). > > For anyone to reproduce this issue, just generate a DSA key using `gpg2 > --gen-key` and select DSA. Then do 'pass init KEYID'. Finally, try to > create a new entry by running 'pass generate -c Facebook 16' and you will > get the 'No public key' messages. > > Best regards, > Santiago > > >
_______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
