Problems with 4096 keys on 2.1 card

Hi, I've been having some problems using a GPG card 2.1 with Ubuntu repo GPG, think it was 2.0.22. I noticed some discussions in Sept-15 about this and got the impression that it should work. Can someone just make a short comment on this, should a 2.0.22 be able to generate 4096 keys and/or impo

Re: Problems with 4096 keys on 2.1 card

On 25 Jan 2016 at 21:07, NIIBE Yutaka wrote: > However, please note that many card readers have problems with larger > APDU. Generating keys on card should be ok, but importing keys would > be failed with bad reader. Signing should be ok, but decryption would > be failed with bad reader. That's

Re: Problems with 4096 keys on 2.1 card

Thanks to you both for commenting on this, I do remember the 335 being one of the most original readers to work without much hazzle. > Please note that GnuPG 1.4 supports up to 3072-bit. This is because > of internal library limitation. > > I believe that "gpg" in Ubuntu is GnuPG 1.4. It is "gp

Re: Problems with 4096 keys on 2.1 card

>> $ gpg2 --card-status >> gpg: selecting openpgp failed: Unsupported certificate > > That is an interesting error message because that one is only used by > gpgsm and not by any components involved in gpg2 --card-status. Please > enter > > gpg-connect-agent -v > > and on its prompt > > SCD GE

fetch yields "rejected by import filter"

Hi, I'm having problems importing and thereafter using keys on another pc. This is kinda annoying since it interfers with using cards smoothly on different computers. I have the privkey on a card, use the admin/fetch command to get the pubkey down and therafter use the card-status to generate the

Re: fetch yields "rejected by import filter"

Hi, > So what happens when you invoke > > $ gpg2 -v --fetch-key [URL]? > > Or for even more verbosity, do -vv. > > HTH, > > Peter. Well, that does work, after I put URL in quotes ("URL"), otherwise it does not. Maybe the 'fetch' command in card-edit/admin is more picky about what URLs actually wo