Bug 1272047 - CA certificate file in PEAP network configuration
CA certificate file in PEAP network configuration
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
x86_64 Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Lubomir Rintel
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-10-15 06:54 EDT by Piuma
Modified: 2016-07-19 15:20 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 15:20:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Piuma 2015-10-15 06:54:38 EDT
Description of problem:

When I configure a new profile for connection with security that use CA cert. I set the option "CA certificate" but Network Manager when try to connect use the /etc/pki/tls/cert.pem instead of my selection.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Fron Network configuration Add profile...
2. Turn ON 802.1x Security
3. Set Authentication to Protected EAP (PEAP)
4. Set CA Certificate
5. Fill others fields if necessary
6. Try to connect

Actual results:
Use my CA file.

Expected results:
In connection it use /etc/pki/tls/cert.pem
Comment 1 Jirka Klimes 2015-10-15 07:51:03 EDT
NetworkManager has an option to use system certificates instead of user provided [1], however it is off by default.

You can check it by
$ nmcli con show "your wifi profile name" | grep system-ca-certs

and changing to "no" (if it was "yes" for some reason)
$ nmcli con modify "your wifi profile name" 802-1x.system-ca-certs no

[1] https://developer.gnome.org/libnm/1.0/NMSetting8021x.html#NMSetting8021x--system-ca-certs

You may be also interested in bug 1236548.
Comment 2 Fedora End Of Life 2016-07-19 15:20:01 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.