This task is more of a support question than a bug report pr feature request.
Details
Jan 19 2018
Jan 12 2018
Let me comment this
I am sharing completed info, please look into it, at may I know the cause
gpg: enabled debug flags: lookup
gpg: DBG: keydb_search: 1 search descriptions:
gpg: DBG: keydb_search 0: SUBSTR: 'JPMCBANK_GPG_PROD_2020'
gpg: DBG: keydb_search: searching keybox (resource 0 of 1)
gpg: DBG: keydb_search: searched keybox (resource 0 of 1) => Success
gpg: DBG: finish_lookup: checking key 88BEBD28 (all)(req_usage=1)
gpg: DBG: checking subkey 022E17B7
gpg: DBG: subkey might be fine
gpg: DBG: using key 022E17B7
gpg: using subkey F423A07D022E17B7 instead of primary key 9D09927E88BEBD28
gpg: DBG: keydb_search: 1 search descriptions:
gpg: DBG: keydb_search 0: SUBSTR: 'JPMCBANK_GPG_UAT_2019'
gpg: DBG: keydb_search: searching keybox (resource 0 of 1)
gpg: DBG: keydb_search: 1 search descriptions:
gpg: DBG: keydb_search 0: LONG_KID: 'BFFCAF61B48701FD'
gpg: DBG: keydb_search: searching keybox (resource 0 of 1)
gpg: DBG: keydb_search: searched keybox (resource 0 of 1) => Success
gpg: DBG: finish_lookup: checking key B48701FD (all)(req_usage=0)
gpg: DBG: using key B48701FD
gpg: using pgp trust model
gpg: DBG: keydb_search: searched keybox (resource 0 of 1) => Success
gpg: DBG: finish_lookup: checking key B48701FD (all)(req_usage=2)
gpg: DBG: checking subkey 403048E0
gpg: DBG: usage does not match: want=2 have=1
gpg: DBG: no suitable subkeys found - trying primary
gpg: DBG: primary key usage does not match: want=2 have=5
gpg: DBG: no suitable key found - giving up
gpg: DBG: keydb_search: 1 search descriptions:
gpg: DBG: keydb_search 0: SUBSTR: 'JPMCBANK_GPG_UAT_2019'
gpg: DBG: keydb_search: searching keybox (resource 0 of 1)
gpg: DBG: keydb_search: searched keybox (resource 0 of 1) => EOF
gpg: JPMCBANK_GPG_UAT_2019: skipped: Unusable public key
gpg: E:\New\steps.txt: sign+encrypt failed: Unusable public key
gpg: secmem usage: 1376/32768 bytes in 3 blocks
Jan 11 2018
Jan 8 2018
You might want to look at: https://wiki.gnupg.org/TroubleShooting#Passphrase_on_the_command_line
Jan 2 2018
Jul 13 2017
Without more information, we can not act on this.
Mar 30 2017
Mar 20 2017
Feb 13 2017
Please ask on the gnupg-users at gnupg.org mailing list for help. Note that you
do not need to subscribe but just a wait a bit until our moderators will approve
your mail. But anyway here is a quick hint in case you did not already tried:
$ gpg --card-edit
gpg/card> admin
gpg/card> factory-reset
Jan 23 2017
Sep 19 2016
This is an issue of GNOME as packaged by Red Hat. Please file a bug in Red
Hat's bug tracker instead.
I don't have sufficient permission to upgrade gnome session, so if you have
any idea suggest me
Use a recent gnome version and you are fine.
Aug 16 2016
This seems to be a general question on how to use the software. Please read the
HOWTOS at gnupg.org and if you still have questions ask at the gnupg-users
mailing list.
Jun 13 2016
scdaemon is part of GnuPG.
OpenSC is entirely unrelated to GnuPG.
Please take this to a mailing list (e.g. gnupg-users)
Jun 6 2016
Ah sorry I understood you were saying the bug is in OpenSC. Where can I report
to scdaemon? I can't find it.
Jun 5 2016
FireFox is not GnuPG and does not support the OpenPGP card.
As I said, the card may work with gpgsm because I once developed support for the
Belgian eID card. But it is likely to need some tweaking (gnupg/scd/app-p15.c)
I saw that it says not supported, but DNIe is actually supported. I can use it
flawlessly with Firefox for instance.
Please see:
https://github.com/OpenSC/OpenSC/wiki/DNIe-%28OpenDNIe%29#update-2013-08-27
https://github.com/OpenSC/OpenSC/issues/774#issuecomment-222468916
Thanks!
Jun 4 2016
Jun 1 2016
May 11 2016
Please ask on the gnupg-users mailibng list for help.