Re: scd: ambiguous certificate IDs for pkcs#15 certificates

2024-02-19 Thread Mario Haustein via Gnupg-devel
Hi Werner, Am Montag, 19. Februar 2024, 16:53:04 CET schrieb Werner Koch: > > It seems the counter is application-global, but collision detection is > > just > > scoped to the object directory. > > Good attach. Please add the attached patch. many thanks! This was really fast. Now it works

Re: scd: ambiguous certificate IDs for pkcs#15 certificates

2024-02-19 Thread Werner Koch via Gnupg-devel
On Mon, 19 Feb 2024 16:33, Mario Haustein said: > your solution sounds much more simpler than mine and should solve the problem > with record files as well. Maybe it's a good idea to separate the counter > from > the ID by an additional '.', isn't it? Much more work and code unfortunately. >

Re: scd: ambiguous certificate IDs for pkcs#15 certificates

2024-02-19 Thread Mario Haustein via Gnupg-devel
Am Montag, 19. Februar 2024, 14:55:11 CET schrieb Werner Koch: > Hi Mario, Hi Werner, > > Is there a way to avoid this unambiguity? Would it for example be possible > > to use the path ID of the certificate file instead of the ID tag in the > > This would not solve the case if we have several

Re: scd: ambiguous certificate IDs for pkcs#15 certificates

2024-02-19 Thread Werner Koch via Gnupg-devel
Hi Mario, > For this card, all certificates have the same ID tag for each key (2 or 3 in > the example), as they are part of the same certificate chain. Thus the I have not checked the specs but I think this is Bad Idea even if allowed. Clearly we will run into problems. > Is there a way to

scd: ambiguous certificate IDs for pkcs#15 certificates

2024-02-16 Thread Mario Haustein via Gnupg-devel
Dear developers, I am currently in the process of implementing the D-Trust ECC smartcards and encountered an issue in the certificate management for PKCS#15 cards. It is not limited to ECC cards and presumably concerns all PKCS#15 cards. When importing the keys and certificates from the