Bug 1480206 - WPA 2 Enterprise doesn't work with SELinux enabled even though certificate file is labelled with home_cert_t
Summary: WPA 2 Enterprise doesn't work with SELinux enabled even though certificate fi...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 26
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-10 12:12 UTC by ell1e
Modified: 2017-08-14 19:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-14 19:08:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ell1e 2017-08-10 12:12:18 UTC
Description of problem:
WPA 2 Enterprise doesn't work with SELinux enabled even though certificate file is labelled with home_cert_t. The only method I managed to connect is by using sudo setenforce 0.

Since there is also no proper error message (I just get repeated Wifi password prompts) I really have no idea why, and I don't know what to do about it. Since this worked on previous Fedora versions with proper certificate file labelling, it seems like a bug / regression.


Version-Release number of selected component (if applicable):
3.13.1-260.3.fc26

How reproducible:
100%

Steps to Reproduce:
1. Configure WPA 2 Enterprise linux wifi with certificate file labelled as home_cert_t
2. Try to connect

Actual results:
repeated password prompts and no useful error, unless sudo setenforce 0 was previously used

Expected results:
works

Additional info:

Comment 1 Daniel Walsh 2017-08-14 13:40:49 UTC
What AVC are you getting?

Comment 2 ell1e 2017-08-14 19:08:40 UTC
I didn't get any sort of visible notification at all, it just plain didn't work.

I realized later my home didn't have proper labels because I copied it from a location without SELinux in the filesystem. Restoring all home labels fixed it!


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