Ubuntu
network-manager package

nm-applet connects to unsecured networks by default

Bug #151869 reported by HappySpaceInvader
10
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

When I first boot up Ubuntu (on an Acer Aspire 5630 laptop), it always connects immediately to the first unsecured wireless network it can find.
In my case, this means I connect to the unsecured wireless network of another company in the same building as me, that they provide for their own visitors. I have no permission to use this network.

In the United Kingdom, It is illegal to connect to a wireless network without the express permission of the owner with the intent of using it to obtain an Internet connection (http://news.bbc.co.uk/1/hi/magazine/6960304.stm). The current behaviour of the Network Manager applet is putting users at risk of being accused of commiting a criminal offence under the Communications Act 2003 and/or the Computer Misuse Act 1990. In such a circumstance, the onus would then be on the user to show that they did not intend to steal the service from the other party.

Network Manager should have the facility to remember the last network you were connected to and use that instead of simply taking the easiest route.

Revision history for this message
Ryan Marquardt (orbnauticus) wrote :

I am also having this problem, where network manager connects to a neighbor's unsecured network first, rather than my own secured connection six feet away. This is, in general, a security risk and should be addressed immediately.

Changed in network-manager-applet:
assignee: nobody → ryan-marquardt
status: New → Incomplete
Ryan Marquardt (orbnauticus)
Changed in network-manager-applet:
assignee: ryan-marquardt → nobody
Revision history for this message
wolfger (wolfger) wrote :

Not seeing why this bug was marked "incomplete". You should only set "incomplete" if:
-you have to ask the reporter questions
-you ask the submitter to provide any necessary information in a comment

I am marking it "new" again in the hopes somebody will pay attention to it.

Changed in network-manager-applet:
status: Incomplete → New
Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

Changed in network-manager-applet:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in network-manager-applet:
status: Incomplete → Invalid
Revision history for this message
HappySpaceInvader (richard-cross) wrote :

Yes, I have the latest version of the application and the issue still occurs. I also managed to test it on Hardy Heron and it still occurs there too.

Revision history for this message
HappySpaceInvader (richard-cross) wrote :

The bug is still very much valid. The latest version of nm-applet doesn't seem to have fixed any of the bugs I have raised against it.

Changed in network-manager-applet:
status: Invalid → New
Revision history for this message
JLR (artirj) wrote :

Confirmed in Hardy

Changed in network-manager-applet:
status: New → Confirmed
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We are wondering if this is still an issue. Can you try it with the latest Ubuntu release or even jaunty? Thanks in advance.

Changed in network-manager-applet:
status: Confirmed → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Endolith (endolith) wrote :

I haven't had it connect to the wrong network in a while, but I'm not sure if it's still a problem in general.

"The current behaviour of the Network Manager applet is putting users at risk of being accused of commiting a criminal offence under the Communications Act 2003 and/or the Computer Misuse Act 1990."

Sounds like you need to file a bug with your lawmakers, too...

Revision history for this message
Alexander Sack (asac) wrote :

if it ever was an issue, its not a problem now anymore.

affects: network-manager-applet (Ubuntu) → network-manager (Ubuntu)
Changed in network-manager (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Alexander Sack (asac) wrote :

btw, its a feature that NM connects against SSIDs you ever connected manually against at some point. so most likely you connected once explicitly and now it reconnects there intentionally.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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