Seams to be resolved with Gpg4win-2.0.1-RC1 (GpgOL 1.0.1-svn308). Needs more
tests of other users. Juicyfruits, can you test again?

Seams to be resolved with Gpg4win-2.0.1-RC1 (GpgOL 1.0.1-svn308). Needs more
tests of other users.

I close this issue, thanks again

We will never get 1.4.10 out if you guys always find bugs :-)

This is not a bug. See the chapter on how to specify a user ID. An 8 character
long string all consisting of valid hex characters is considered a key ID (in
your case 0x0564B63A). There are explicit ways to mark a user ID; for example:

No time to look into this. Hints on how to fix this are of course welcomes

Marcus: I recall that you recently changed something in the cancel code - is
that his problem?

Sorry, we can't read doc files on our development machines.
If that inhcludes a screenshot, it won't help too much, we need a more detailed
error description. See "Add debug information" at
http://www.gpg4win.org/reporting-bugs.html .

I've just change the tittle, because for me whent I look the differents logs files :

Sorry, I typoed, it was 3072R that I generated and failed to use. Its the same
type of key used in T1105. A 2048R key works
fine.

D102: 246_gpgme-1.1.8-closefiledescriptor.patch

here scdaemon log :

And why you won't fix it?

Last informations from gpg-agent.log :

Duplicate of T1102

You are right. See also T1102.

I was about to write: That is known and we won't fix it. That it works in
1.4.9 is interesting. I need to look at it.

Duplicate of T1107

See T1107 - it is the same cause.

Is "3074G bit" a type or do you really try to use an Elgamal key? The card does
only support RSA keys.

Refocussing this issue on the "hang" symptom.

Is there any more information I can provide? Can you reproduce it?

test sign + encryption in debug mode :

I did some more debugging on this, it seems something can't handle the large
APDU messages generated when doing decryption with a 3072-bit key. Checking the
ISO documentation, a 64xx error is an execution error, so it seems either a bad
request is going to the card, or the card simply can't handle a long message:

Here more informations :

ok, please close off this bug and I will move to latest version.

ok, please close off this bug and I will move to latest version.

I changed the e-mail address in the attached ndr.txt to all x

ok, you can close off this bug report. I will move to newer version.

I had a go at doing this in sections. I used:

Sorry please delete also, I've solve my problem.

please delete this, thanks in advanced

I remember that I had a similar problem in a previous version which I reported
but I can't remember on which site/community. In a following version the bug has
been fixed and I never had this problem again up to and including version 0.9.92.
That's strange beacause you said that's is an existing problem since years.