Filenames with spaces not accepted when connecting to certificate-authenticated wifi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
* Impact
Using an authentification certificate with a filename in its name is not possible
* Test case
- connect to a wpa wifi needing a certificate
- name the certificate to include a space
- try to use that said certificate
it should be possible to use it
* Regression potential
the change is on the function dealing with the filename/uri for certificate, make sure those keep working on different locations with names including spaces or not
*******************
This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS
When connecting to a certificate-
Unexpected behaviour: If any of the files have spaces in their filenames, after choosing them in the file picker the field is highlighted by a red box, and the 'Connect' button is greyed out.
This is depicted in the attachment network-
There is also no explanation offered for why the red box highlight is present - no tooltip, no help from pressing F1, no popup, and as far as I can find no logs.
If you move/rename the file, so there are no spaces in the filename, the problem is worked around.
The problem is not present on the edit connection dialogue; filenames with spaces are acceptable there.
The problem was also not present on Ubuntu 16.04, and users who upgrade from 16.04 to 18.04 will find their connection keeps working. It is only when creating an entirely new connection (or after forgetting the connection and recreating it) that the problem dialog appears.
Adding wpa2-tls- root-cert- no-spaces. png which shows settings are acceptable, the red box disappears and the connect button becomes available when file is renamed to remove spaces.