Adding NFS shares with GUI has scary behavior when a folder has spaces between words
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Create a 'Shared' folder in /home/username
Create a 'Shared 192.168.1.100' folder in /home/username
Right click 'Shared' and go to 'Share Folder'. Add a NFS share with no allowed IP addresses.
Right click 'Shared 192.168.1.100'. Add a NFS share with no allowed IP addresses.
Go to 'System' - 'Administration' - 'Shared Folders'
You will now see only one share, '/home/
This does change the /etc/exports file, and I believe it may be a security vulnerability.
Doing this with a folder with three words (two spaces) adds each word after the space to hosts allowed to access (read-only) the share.
Seems like it would be important for users to share a folder with spaces in it, especially for everyday desktop use.
Changed in nfs-utils: | |
status: | New → Confirmed |
Changed in nfs-utils (Ubuntu): | |
importance: | Undecided → Low |
I can also confirm this.
A slightly educated guess would hypothesize that the GUI doesn't like the backslashes that are needed in the path, because when the needed backslash is manually added to /etc/exports, the 'Shared Folders' GUI comes up with an error when trying to view the properties for the share saying that the folder cannot be found. After closing the error dialog box and the properties box, the share is changed to '/home/username' with the same properties as the intended folder.
The above stated behavior also occurs when a folder is added just using the 'Shared Folders' dialog.