Description of problem: Using a pkcs11 token, network manager is unable to use the pin (even if provided correctly). connection.id: Blackhats connection.uuid: 3c6970fa-0592-4bb1-a7cb-f81b05baade0 connection.stable-id: -- connection.interface-name: -- connection.type: 802-11-wireless connection.autoconnect: yes connection.autoconnect-priority: 0 connection.autoconnect-retries: -1 (default) connection.timestamp: 0 connection.read-only: no connection.permissions: -- connection.zone: -- connection.master: -- connection.slave-type: -- connection.autoconnect-slaves: -1 (default) connection.secondaries: -- connection.gateway-ping-timeout: 0 connection.metered: unknown connection.lldp: -1 (default) 802-1x.eap: tls 802-1x.identity: william 802-1x.anonymous-identity: -- 802-1x.pac-file: -- 802-1x.ca-cert: /home/william/secure/user_cert/bh_ldap_ca.crt 802-1x.ca-cert-password: <hidden> 802-1x.ca-cert-password-flags: 0 (none) 802-1x.ca-path: -- 802-1x.subject-match: -- 802-1x.altsubject-matches: -- 802-1x.domain-suffix-match: -- 802-1x.client-cert: pkcs11:model=PKCS%2315%20emulated;manufacturer=piv_II;serial=00000000;token=PIV%20Card%20Holder%20pin%20%28PIV_II%29;id=%04 802-1x.client-cert-password: <hidden> 802-1x.client-cert-password-flags: 0 (none) 802-1x.phase1-peapver: -- 802-1x.phase1-peaplabel: -- 802-1x.phase1-fast-provisioning: -- 802-1x.phase1-auth-flags: 0 (none) 802-1x.phase2-auth: -- 802-1x.phase2-autheap: -- 802-1x.phase2-ca-cert: 0 (none) 802-1x.phase2-ca-cert-password: -- 802-1x.phase2-ca-cert-password-flags: <hidden> 802-1x.phase2-ca-path: -- 802-1x.phase2-subject-match: -- 802-1x.phase2-altsubject-matches: -- 802-1x.phase2-domain-suffix-match: -- 802-1x.phase2-client-cert: -- 802-1x.phase2-client-cert-password: <hidden> 802-1x.phase2-client-cert-password-flags:0 (none) 802-1x.password: <hidden> 802-1x.password-flags: 0 (none) 802-1x.password-raw: <hidden> 802-1x.password-raw-flags: 0 (none) 802-1x.private-key: pkcs11:model=PKCS%2315%20emulated;manufacturer=piv_II;serial=00000000;token=PIV%20Card%20Holder%20pin%20%28PIV_II%29;id=%04 802-1x.private-key-password: <hidden> 802-1x.private-key-password-flags: 0 (none) 802-1x.phase2-private-key: -- 802-1x.phase2-private-key-password: <hidden> 802-1x.phase2-private-key-password-flags:0 (none) 802-1x.pin: <hidden> 802-1x.pin-flags: 0 (none) 802-1x.system-ca-certs: no 802-1x.auth-timeout: 0 802-11-wireless.ssid: Blackhats 802-11-wireless.mode: infrastructure 802-11-wireless.band: -- 802-11-wireless.channel: 0 802-11-wireless.bssid: -- 802-11-wireless.rate: 0 802-11-wireless.tx-power: 0 802-11-wireless.mac-address: 68:A8:6D:4F:33:88 802-11-wireless.cloned-mac-address: -- 802-11-wireless.generate-mac-address-mask:-- 802-11-wireless.mac-address-blacklist: -- 802-11-wireless.mac-address-randomization:default 802-11-wireless.mtu: auto 802-11-wireless.seen-bssids: -- 802-11-wireless.hidden: no 802-11-wireless.powersave: default (0) 802-11-wireless-security.key-mgmt: wpa-eap 802-11-wireless-security.wep-tx-keyidx: 0 802-11-wireless-security.auth-alg: open 802-11-wireless-security.proto: -- 802-11-wireless-security.pairwise: -- 802-11-wireless-security.group: -- 802-11-wireless-security.leap-username: -- 802-11-wireless-security.wep-key0: <hidden> 802-11-wireless-security.wep-key1: <hidden> 802-11-wireless-security.wep-key2: <hidden> 802-11-wireless-security.wep-key3: <hidden> 802-11-wireless-security.wep-key-flags: 0 (none) 802-11-wireless-security.wep-key-type: 0 (unknown) 802-11-wireless-security.psk: <hidden> 802-11-wireless-security.psk-flags: 0 (none) 802-11-wireless-security.leap-password: <hidden> 802-11-wireless-security.leap-password-flags:0 (none) ipv4.method: auto ipv4.dns: -- ipv4.dns-search: -- ipv4.dns-options: (default) ipv4.dns-priority: 0 ipv4.addresses: -- ipv4.gateway: -- ipv4.routes: -- ipv4.route-metric: -1 ipv4.ignore-auto-routes: no ipv4.ignore-auto-dns: no ipv4.dhcp-client-id: -- ipv4.dhcp-timeout: 0 ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: -- ipv4.dhcp-fqdn: -- ipv4.never-default: no ipv4.may-fail: yes ipv4.dad-timeout: -1 (default) ipv6.method: auto ipv6.dns: -- ipv6.dns-search: -- ipv6.dns-options: (default) ipv6.dns-priority: 0 ipv6.addresses: -- ipv6.gateway: -- ipv6.routes: -- ipv6.route-metric: -1 ipv6.ignore-auto-routes: no ipv6.ignore-auto-dns: no ipv6.never-default: no ipv6.may-fail: yes ipv6.ip6-privacy: -1 (unknown) ipv6.addr-gen-mode: stable-privacy ipv6.dhcp-send-hostname: yes ipv6.dhcp-hostname: -- ipv6.token: -- proxy.method: none proxy.browser-only: no proxy.pac-url: -- proxy.pac-script: -- Version-Release number of selected component (if applicable): NetworkManager-1.8.2-1.fc26.x86_64 How reproducible: Always Steps to Reproduce: 1. Use an external CCID device that requires a pin or interaction 2. Use this as the private key/cert for the connection 3. Actual results: Connection fails for no reason, and device does not activate Expected results: Ability to authenticate with pkcs11 device. Additional info: Tested with a yubikey ccid device that requires pin + touch. # p11-kit list-modules opensc: opensc-pkcs11.so library-description: OpenSC smartcard framework library-manufacturer: OpenSC Project library-version: 0.17 token: PIV Card Holder pin (PIV_II) manufacturer: piv_II model: PKCS#15 emulated serial-number: 00000000 flags: rng login-required user-pin-initialized token-initialized # p11tool --list-tokens Token 6: URL: pkcs11:model=PKCS%2315%20emulated;manufacturer=piv_II;serial=00000000;token=PIV%20Card%20Holder%20pin%20%28PIV_II%29 Label: PIV Card Holder pin (PIV_II) Type: Hardware token Manufacturer: piv_II Model: PKCS#15 emulated Serial: 00000000 Module: opensc-pkcs11.so
Created attachment 1323016 [details] Network Manager debug log from nmcli con up
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.