Bug 1154723
| Summary: | PKCS11-Helper (and OpenVPN) does not work with latest SafeNet/Aladdin hardware eTokens | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sven Anders <anders> | ||||
| Component: | pkcs11-helper | Assignee: | Kalev Lember <kalevlember> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 21 | CC: | alonbl, kalevlember | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-12-02 04:25:38 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 948611 [details]
Patch with correction and addtional error output
Thanks for the patch. Can you submit it upstream for review, please? https://github.com/OpenSC/pkcs11-helper This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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 20 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. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. |
Description of problem: If I try to use SafeNet/Aladdin eTokens with OpenVPN (which uses the pkcs11-helper library), I get the following error: # openvpn --show-pkcs11-ids /usr/lib64/pkcs11/libeTPkcs11.so Mon Oct 20 16:21:22 2014 PKCS#11: Cannot add provider '/usr/lib64/libeTPkcs11.so' 6-'CKR_FUNCTION_FAILED' Mon Oct 20 16:21:22 2014 Exiting due to fatal error Version-Release number of selected component (if applicable): pkcs11-helper: 1.11 openvpn: 2.3.2 How reproducible: Always Steps to Reproduce: 1. Install eToken libraries 2. Insert token 3. Use the given command: openvpn --show-pkcs11-ids <path to provider library> Actual results: Outputs error Expected results: List of available Tokens / Slots Additional info: I tracked the bug down to the pkcs11-helper library. I added additional error output to the pkcs11-helper library by simply adding the output of dlerror(). Then I saw the reason of the failure: dlopen error: /usr/lib/pkcs11/provider.so: undefined symbol: libhal_device_get_property_bool In fact, the problem lies in the vendors pkcs11 provider library. But because the function is not used, we can use the "RTLD_LAZY" instead of "RTLD_NOW" in the dlopen() command. I do know, the is change has security related implications, but I think this change should be (mostly) harmless. On the other hand, if you want, you could make this an config option or try this command after the RTLD_NOW command failed and issue an warning. Moreover, the second addition in the patch, is this additional error output, which could me very useful!