[Triage-desktop] [Bug 5125] New: drakx-net does not configure WPA Enterprise connections correctly.
bugzilla-daemon at rosalab.ru
Tue Mar 3 07:09:38 MSK 2015
Bug ID: 5125
Assignee: triage-desktop at lists.rosalab.ru
Summary: drakx-net does not configure WPA Enterprise
QA Contact: triage-desktop at lists.rosalab.ru
Classification: ROSA Desktop
RPM Package: drakxtools
Reporter: zombie_ryushu at yahoo.com
Component: -Enter Bugs Here-
Product: Desktop Bugs
Created attachment 3777
WPA Supplicant Patch.
Description of problem:
When using mcc to configure WPA Enterprise connections the following occurs:
1. If a user enters a private key password it is shown on screen.
This is inconvenient, as a unprivileged user could see the password as it's
being typed in or copied. Considering that mcc hides the other passwords, it
may as well hide this one. (Consistency.)
2. If a user configures the following: Private key, Private key password, or a
CA cert they are not saved as strings in /etc/wpa_supplicant.conf.
This means that the connection will not come up as wpa_supplicant will not
parse the private key password, or the paths correctly, and will not load them
as a result.
I'm attaching a patch that fixes the above.
Steps to Reproduce:
1. Open mcc
2. Try to configure a WPA Enterprise network.
3. Watch the connection not come up. (And the password has been exposed.)
This is part of the initiative to support FreeRadius, Samba 4, and OpenLDAP
based applications better. For that reason, this is being CCed to the Samba 4
Maintainer working on both Samba 4 and OpenLDAP.
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Triage-desktop