Hide Forgot
Created attachment 551690 [details] Copy of the offical patch from RedHat. Description of problem: When inserting ActivKey USB Token in to a Fedora 16 running laptop. pkcs11_listcerts or pkcs11_inspect and etc does not prompt for a password nor does it display the certificates. The reason is that it is missing the patch that allowed certs that did not exists in slot_0 work. Version-Release number of selected component (if applicable): 1.1.0-15 - 1.1.0-19 How reproducible: install coolkey or part of the fedora base installation. Insert an ActivKey Token that is Grey not the blue one. as root or as an user run pkcs11_listcerts debug and nothing returns stating no card available or to that suggestion. download the patch at https://bugzilla.redhat.com/attachment.cgi?id=500732 download the 1.1.0-19 src.rpm Steps to Reproduce: 1.Download the ActivKey Patch from Fedora Bug save it as coolkey-activkey.patch https://bugzilla.redhat.com/attachment.cgi?id=500732 2.Change Directory to coolkey-1.1.0/ 3. Patch this order 1) patch -p0 < ../coolkey-cache-dir-move.patch (Aug 15th, 2007) 2) patch -p1 < ../coolkey-gcc43.patch (Feb 13th, 2008) 3) patch -p1 < ../coolkey-latest.patch (Sep 11th, 2009) 4) patch -p1 < ../coolkey-simple-bugs (Sep 16th, 2009) 5) patch -p0 < ../coolkey-thread-fix.patch (Dec 18th, 2009) 6) patch -p1 < ../coolkey-cac.patch (Jun 16th, 2010) 7) patch -p1 < ../coolkey-cac-1.patch (Jun 23rd, 2010) 8) patch -p1 < ../coolkey-pcsc-lite-fix.patch (Sep 8th 2010) 9) patch -p2 < ../coolkey-activkey.patch (May 23rd, 2011) * you should only see succeeded messages if you get failure or prompted for the file you have a typo or you are in the wrong directory. If you cut and paste the above you need to remove the dates that I have on the end. 4.autoconf for 64bit system ./configure --libdir=/usr/lib64/ (check for errors) for 32bit system ./configure --libdir=/usr/lib/ (check for errors) 5. make (check for errors) sudo make install 6. or copy the newly created libcoolkeypk11.so from ~/src/rpm/SOURCES/coolkey-1.1.0/src/coolkey/.libs/ to /usr/lib64/pkcs11/ Actual results:pkcs11_inspect No prompt just returns with no results Expected results: PIN for token: Printing data for mapper cn: John Doe Printing data for mapper pwent: John Doe Printing data for mapper subject: E=john.doe,CN=John Doe,OU=VPN-WEB-H,OU=Employment Status - Employees,O=Hewlett-Packard Company Additional info: Please incorporate the RedHat Patch back into the coolkey source. Attached is the patch.
Please fix it. AK does not work at the moment withaout the patch.
Same issue on RHEL6.2 with coolkey-1.1.0-19.el6, please fix.
Fix issue in Fedora16 with latest coolkey rpm coolkey-1.1.0-20.fc17.x86_64.rpm http://koji.fedoraproject.org/koji/buildinfo?buildID=284096
That's weird -20 is just a rebuild of -19.
(In reply to comment #4) > That's weird -20 is just a rebuild of -19. Just for the record - fresh F16, upgraded coolkey to -20, but the issue is still present.
This problem still exists. Coolkey-1.1.0-19.FC15 and later are missing the coolkey patch stated in this bug report. Coolkey-1.1.0-20.fc17 is still missing the code that will allow the use of the Activkey Token. Opening new bug.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Let's not loose this bug just because f16 is end of life. pushing it forward to rawhide
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Issue still seems to be very much present in both Fedora 18 and Fedora 19 running coolkey-1.1.0-21.fc18.x86_64 and coolkey-1.1.0-23.fc19.x86_64 respectively.
Still not fixed in F20?
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.