Bug 1056768 - NetworkManager connection names do not escape ampersands
Summary: NetworkManager connection names do not escape ampersands
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 20
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-22 21:42 UTC by Scott K Logan
Modified: 2015-06-29 14:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:40:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
nm-connection-editor console messages (267 bytes, text/plain)
2014-01-22 21:42 UTC, Scott K Logan
no flags Details

Description Scott K Logan 2014-01-22 21:42:05 UTC
Created attachment 854049 [details]
nm-connection-editor console messages

Description of problem:
When a connection is created through Gnome, the created connection's name does not use & - simply uses &.
Using nm-connection-editor floods the terminal with warnings about the fault, but does not fail to modify the connection.

Manually adding & to the connection works fine - both editors show the connection correctly. However, the next time NetworkManager modifies the configuration, the & are replaced with & again.

Version-Release number of selected component (if applicable):
NetworkManager-1:0.9.9.0-25.git20131003.fc20.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a connection with & in the name
2. Open nm-connection-editor
3. Observe console messages

Actual results:
nm-connection-editor warns about improper name, configuration file indeed does not contain them.

Expected results:
Ampersands are escaped as & as they should be.

Additional info:

Comment 1 Fedora End Of Life 2015-05-29 10:37:35 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 14:40:07 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
bug.

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.