Back to bug 1877973
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2020-09-10 22:54:18 UTC | Pool ID | sst_security_crypto_rhel_8 | |
| Jakub Jelen | 2020-09-11 07:55:40 UTC | Keywords | Regression, Triaged | |
| Priority | unspecified | medium | ||
| Link ID | Github OpenSC/OpenSC/issues/1922 | |||
| Doc Text | Cause: Some card drivers specifying both specific PIN label and token label cause TOKEN_INFO label to be incorrectly padded with spaces on the left. Consequence: Token labels are padded with spaces on the left, causing issues for various applications handling pkcs11 URIs (p11tool) or existing configurations. Workaround (if any): temporarily update existing configuration to match current URIs or skip the token= part if the objects can be identified uniquely using other identifiers. Result: Applications with this configuration handle the uris correctly. | |||
| Doc Type | If docs needed, set a value | Known Issue | ||
| Khushbu Borole | 2020-09-14 08:47:27 UTC | CC | kborole | |
| Docs Contact | kborole | |||
| Khushbu Borole | 2020-09-24 14:22:19 UTC | CC | jjelen | |
| Flags | needinfo?(jjelen) | |||
| Jakub Jelen | 2020-09-24 17:35:36 UTC | Flags | needinfo?(jjelen) | |
| Khushbu Borole | 2020-09-25 05:29:27 UTC | Doc Text | Cause: Some card drivers specifying both specific PIN label and token label cause TOKEN_INFO label to be incorrectly padded with spaces on the left. Consequence: Token labels are padded with spaces on the left, causing issues for various applications handling pkcs11 URIs (p11tool) or existing configurations. Workaround (if any): temporarily update existing configuration to match current URIs or skip the token= part if the objects can be identified uniquely using other identifiers. Result: Applications with this configuration handle the uris correctly. | .*pkcs11* token label in smart card has extra padding Card drivers that specify a *PIN* label and a *token* label causes the `TOKEN_INFO` label to be incorrectly padded by adding spaces on the left. Consequently, leading to issues for applications handling *pkcs11* URIs or existing configurations. As a workaround, you need to temporarily update the existing configuration to match the current URIs or skip the `TOKEN_INFO` label if the objects can be identified uniquely using other identifiers for example serial number, object label, object id, etc. As a result, with the workaround configuration, the applications can handle URIs as expected. |
| Khushbu Borole | 2020-09-25 13:56:30 UTC | Doc Text | .*pkcs11* token label in smart card has extra padding Card drivers that specify a *PIN* label and a *token* label causes the `TOKEN_INFO` label to be incorrectly padded by adding spaces on the left. Consequently, leading to issues for applications handling *pkcs11* URIs or existing configurations. As a workaround, you need to temporarily update the existing configuration to match the current URIs or skip the `TOKEN_INFO` label if the objects can be identified uniquely using other identifiers for example serial number, object label, object id, etc. As a result, with the workaround configuration, the applications can handle URIs as expected. | .`pkcs11` token label for smart cards has extra padding Card drivers that specify a *PIN* label and a *token* label incorrectly pad the `TOKEN_INFO` label by adding spaces to the left. This causes issues for applications handling `pkcs11` URIs or existing configurations. To work around this problem, temporarily update the existing configuration to match the current URIs, or skip the `TOKEN_INFO` label if the objects can be identified uniquely using other identifiers, such as, serial numbers, object labels, object ids, and so on. As a result, with the workaround configuration, the applications can handle URIs as expected. |
| Sneha Veeranki | 2020-10-22 21:40:35 UTC | CC | sveerank | |
| Jakub Jelen | 2020-10-26 09:55:00 UTC | Status | NEW | MODIFIED |
| Fixed In Version | opensc-0.20.0-3.el8 | |||
| errata-xmlrpc | 2020-10-26 10:00:10 UTC | Status | MODIFIED | ON_QA |
| Sneha Veeranki | 2020-10-29 18:31:30 UTC | Status | ON_QA | VERIFIED |
| Red Hat One Jira (issues.redhat.com) | 2020-10-29 18:35:07 UTC | Link ID | Red Hat Issue Tracker - Private RHELPLAN-53683 | |
| Jakub Jelen | 2020-12-11 14:02:02 UTC | Doc Text | .`pkcs11` token label for smart cards has extra padding Card drivers that specify a *PIN* label and a *token* label incorrectly pad the `TOKEN_INFO` label by adding spaces to the left. This causes issues for applications handling `pkcs11` URIs or existing configurations. To work around this problem, temporarily update the existing configuration to match the current URIs, or skip the `TOKEN_INFO` label if the objects can be identified uniquely using other identifiers, such as, serial numbers, object labels, object ids, and so on. As a result, with the workaround configuration, the applications can handle URIs as expected. | Cause: The bug in RHEL 8.3 caused that token label of some smart cards had wrong padding. Consequence: The wrong padding could cause issues to match card based on this attribute in PKCS#11 URIs in different applications. Fix: The padding was fixed in RHEL 8.4 for all cards. Result: Previously defined PKCS#11 URIs and matching against them in application should work as expected. (old doc text from Known Issue): .`pkcs11` token label for smart cards has extra padding Card drivers that specify a *PIN* label and a *token* label incorrectly pad the `TOKEN_INFO` label by adding spaces to the left. This causes issues for applications handling `pkcs11` URIs or existing configurations. To work around this problem, temporarily update the existing configuration to match the current URIs, or skip the `TOKEN_INFO` label if the objects can be identified uniquely using other identifiers, such as, serial numbers, object labels, object ids, and so on. As a result, with the workaround configuration, the applications can handle URIs as expected. |
| Doc Type | Known Issue | Bug Fix | ||
| Khushbu Borole | 2021-03-29 19:15:20 UTC | Doc Text | Cause: The bug in RHEL 8.3 caused that token label of some smart cards had wrong padding. Consequence: The wrong padding could cause issues to match card based on this attribute in PKCS#11 URIs in different applications. Fix: The padding was fixed in RHEL 8.4 for all cards. Result: Previously defined PKCS#11 URIs and matching against them in application should work as expected. (old doc text from Known Issue): .`pkcs11` token label for smart cards has extra padding Card drivers that specify a *PIN* label and a *token* label incorrectly pad the `TOKEN_INFO` label by adding spaces to the left. This causes issues for applications handling `pkcs11` URIs or existing configurations. To work around this problem, temporarily update the existing configuration to match the current URIs, or skip the `TOKEN_INFO` label if the objects can be identified uniquely using other identifiers, such as, serial numbers, object labels, object ids, and so on. As a result, with the workaround configuration, the applications can handle URIs as expected. | .Improved padding for *pkcs11* token label Previously, the *pkcs11* token label had extra padding in some smart cards. As a consequence, the wrong adding caused issue matching cards based on the attributes. With this update, the padding is fixed for all the cards and defined PKCS#11 URIs and matching against them in application should work as expected. |
| Flags | needinfo?(jjelen) | |||
| Jakub Jelen | 2021-03-29 20:45:57 UTC | Flags | needinfo?(jjelen) | |
| Khushbu Borole | 2021-03-30 08:14:19 UTC | Doc Text | .Improved padding for *pkcs11* token label Previously, the *pkcs11* token label had extra padding in some smart cards. As a consequence, the wrong adding caused issue matching cards based on the attributes. With this update, the padding is fixed for all the cards and defined PKCS#11 URIs and matching against them in application should work as expected. | .Improved padding for `pkcs11` token label Previously, the `pkcs11` token label had extra padding for some smart cards. As a consequence, the wrong padding could cause issues matching cards based on the label attribute. With this update, the padding is fixed for all the cards and defined PKCS #11 URIs and matching against them in application should work as expected. |
| errata-xmlrpc | 2021-05-18 00:40:34 UTC | Status | VERIFIED | RELEASE_PENDING |
| Jan Fiala | 2021-05-18 11:13:48 UTC | CC | jafiala | |
| Doc Text | .Improved padding for `pkcs11` token label Previously, the `pkcs11` token label had extra padding for some smart cards. As a consequence, the wrong padding could cause issues matching cards based on the label attribute. With this update, the padding is fixed for all the cards and defined PKCS #11 URIs and matching against them in application should work as expected. | .Improved padding for `pkcs11` Previously, the `pkcs11` token label had extra padding for some smart cards. As a consequence, the wrong padding could cause issues matching cards based on the label attribute. With this update, the padding is fixed for all the cards and defined PKCS #11 URIs and matching against them in application should work as expected. |
||
| errata-xmlrpc | 2021-05-18 14:46:59 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2021-05-18 14:46:59 UTC |
Back to bug 1877973