| Summary: | app-crypt/gnupg - gpg --disable-ccid option when using pcmcia based cardreader | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Harvey Muller <hlmuller> |
| Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | enhancement | CC: | alonbl |
| Priority: | High | ||
| Version: | 2006.0 | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info data for initial report | ||
|
Description
Harvey Muller
2006-07-21 06:03:57 UTC
Please, always include ebuild name and version plus emerge --info when reporting bugs. Created attachment 92417 [details]
emerge --info data for initial report
As requested, and will do in the future.
ebuild name / version / USE flags:
app-crypt/gnupg-1.9.20-r3 USE="smartcard -X -caps -gpg2-experimental -ldap -nls"
See attachment 92417 [details] (created 2006-07-21 07:32 PST) for emerge --info
UPDATE: Although this 'seemed' to resolve the problem (tested on two different cards, only generating primary keys on the card), the problem continued to persist when I generated subkeys to add to the card. The same general error was present. Through trial and error, what seemed to help, was typing a bunch of junk into a dummy document to help increase random number generation, then generating a subkey. I was able to create three subkeys on the card using this approach. So maybe this is an issue with the application not getting enough random bits? I don't know enough to be sure, but that's my hunch. Hello, I cannot really understand the problem. Can you please try to add some more description? Which cards do you use? Which readers do you use? Is there any other application where card work? Do you use pcsc-lite reader drivers, or relay on gnupg ccid implementation? Thanks! As per comment #5 - need a bit more info. Please reopen when you attach it. |