-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
krb5_child couldn't parse pkcs11 objects if token label contains semicolon #7746
Comments
may be it's a problem of krb5 or p11-kit. I'm not so dived in your code |
Hi, thank you for your report. It looks like libkrb5 does not support escaping the bye, |
libkrb5 expects the Smartcard identifiers like token name or label in a single strings separated by ':'. If one of the identifiers contain a ':' this breaks and since libkrb5 currently does not support escaping of ':' SSSD will ignore the Smartcard during its pre-auth step to determine the available authentication methods and will error out if this happens during the actual authentication step. Resolves: SSSD#7746
Do I need to report a bug in krb5 repo, or will you do that? |
Hi, I opened a ticket asking to at least document this limitation. bye, |
libkrb5 expects the Smartcard identifiers like token name or label in a single strings separated by ':'. If one of the identifiers contain a ':' this breaks and since libkrb5 currently does not support escaping of ':' SSSD will ignore the Smartcard during its pre-auth step to determine the available authentication methods and will error out if this happens during the actual authentication step. Resolves: SSSD#7746
libkrb5 expects the Smartcard identifiers like token name or label in a single strings separated by ':'. If one of the identifiers contain a ':' this breaks and since libkrb5 currently does not support escaping of ':' SSSD will ignore the Smartcard during its pre-auth step to determine the available authentication methods and will error out if this happens during the actual authentication step. Resolves: SSSD#7746
Hi!
I think it could be dangerous too. If token label contains a semicolon, then krb5_child stop read token objects properly. I think it could be a backdoor, because we can pass any pkcs11 lib in this name. Also, I'm not sure what could happen if semicolon will be another object id parts. For example, in object label
Example:
Token name:
Token label: Rutoken ECP <no label> pkcs11:mo
Got this in log:
krb5_child.log
The text was updated successfully, but these errors were encountered: