Even it is annoying to be asked for a password when not editing the network 
settings.
Just ignoring the failure and searching for another network is the best thing 
to do when an access point cannot be connected to.

Probably we could have some settings where we could choose to do the following 
things
 - Pin the client to a specific host (MAC address where authentication was done 
with and not allowing to connect to different hardware, probably a good idea 
for most home networks, but will most likely not work with networks like 
FreeWifi)
 - Prefer the authenticated host when available, but do not pin the client to 
it.
 - Connect to any host with matching SSID with no preference.
This setting is necessary for each authenticated SSID, so that we can configure 
our home network different from the FreeWifi used everywhere else.

Pinning the client to an access point could improve security a bit as it 
prevents connecting to another (malicious?) access point with the same SSID 
without user's knowledge.
A malicious access point could be used for man-in-the-middle attacks.

But it is not impossible to clone an access point with the same MAC, but those 
cloned access points would then probably interfere with each other if they are 
near to each other.
That would make a man-in-the-middle attack a bit harder.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/615239

Title:
  Every Wi-Fi disconnection is treated as an authentication error

Status in Canonical System Image:
  Confirmed
Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I'm using lucid, with the 0.8-0ubuntu3, in a laptop, and is incredible that 
the nm-applet couldn't diagnostic why the wireless connection was lost and only 
trow the password prompt when I've lost the signal. nm-applet should see the 
kern.log or dmesg to react at signal lost. For example, when the kernel try 3 
times probe the AP and don't get response nm-applet say The pc are far away 
from the access point and can not be connected. Please, move close to the 
access point or try another more near. And by the way, when the authentication 
fails, or the association.
  --- 
  Architecture: i386
  CRDA: Error: [Errno 2] No existe el archivo o directorio
  CheckboxSubmission: ee8ebec101005ce57a9c3355b36ca8a7
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  DistroRelease: Ubuntu 10.04
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  IpRoute:
   172.16.254.0/24 dev wlan1  proto kernel  scope link  src 172.16.254.5  
metric 2 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   default via 172.16.254.200 dev wlan1  proto static
  Keyfiles: Error: [Errno 2] No existe el archivo o directorio
  Package: network-manager 0.8-0ubuntu3
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_DO.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  RfKill:
   0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
  Tags: lucid
  Uname: Linux 2.6.32-24-generic i686
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/615239/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to