User-defined connection names don't appear as choices in drop-down menu

Bug #480494 reported by Finog
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NetworkManager
Invalid
Undecided
Unassigned
Ubuntu network, Bluetooth, keyboard menus
Invalid
Undecided
Unassigned
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu 9.10
network-manager 0.9.4.0-0ubuntu3, Ubuntu 12.04 beta

1. From the network menu, choose "Edit Connections...", then "Wireless".
2. Select a wi-fi network that was in the menu (for example, the one you are currently connected to) and choose "Edit".
3. In the "Connection name" field, enter "Fred", and choose Save.
4. Open the menu.

What you see: The previous network name.
What you should see: "Fred".

In the "Network Connections" dialog it is possible for me to set my own custom "Connection Names". One set, networks appear using these names in the Network Connections dialog.

Now, I click on the nm tray applet and it shows me a list of networks, but the networks are named based on their SSID's - not based on the names that I've supposedly given them!

This can be very frustrating if you live in a place where everyone's network is named "linksys".

Insofar as this presents the user with potentially confusing or ambiguous connection options it allows an attacker to set up their own network mirroring the existing network's SSID and thus encourage illegitimate connections. Presenting the user's own defined names is one way of avoiding this (especially if these were say, italicized, to better show that they are trusted networks).

Revision history for this message
Finog (finog) wrote :
Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
Revision history for this message
Olli Ries (ories) wrote :

please reopen if this issue still exists in Ubuntu 12.04

Changed in ubuntu-indicator-mods:
status: New → Incomplete
Changed in network-manager-applet (Ubuntu):
status: New → Incomplete
Changed in network-manager-applet (Ubuntu):
status: Incomplete → Confirmed
Changed in ubuntu-indicator-mods:
status: Incomplete → Confirmed
description: updated
Thomas Hood (jdthood)
tags: added: precise
Thomas Hood (jdthood)
Changed in ubuntu-indicator-mods:
status: Confirmed → Invalid
affects: network-manager-applet (Ubuntu) → network-manager (Ubuntu)
Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

This seems to be an upstream issue. Would you be able to report this bug upstream?:

https://bugs.launchpad.net/bugs/bugtrackers/gnome-bugs

Please refer to this bug and update this bug report to be linked to the new report.

tags: added: quantal
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

I'm going to close this bug report as their is nothing else we can do with this old report in a now unsupported version of Ubuntu.

Changed in network-manager:
status: New → Invalid
Changed in network-manager (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.