Public bug reported:
When a WiFi connection behaves unstable over longer time (eg. long
range), sometimes the user is asked for the password again (the
requester come up already filled), even if it is correct. The request
can come up at any time, depending on the connection quality, and likely
force the user to look up the already correctly entered password again.
This is very annoying for kiosk-like systems or when using fullscreen
apps.
This bug is stone old and iv'e seens this year by year over a broad
range of Ubuntu versions as well devices (Intel and ARM platform). It
still happens as of Ubuntu 16.04.
So I wonder if this is inevitable by the fact that NetworkManager
sometimes can't decide between an authetication failed by wrong password
vs. authentication failed by bad connection. If not, it should finally
be fixed.
There may be a security problem, for locked down kiosk applications, as
the password may be obtained by kiosk users if the request pops up.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
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/1633413
Title:
Obsolete authenthication requests for WiFi
Status in network-manager package in Ubuntu:
New
Bug description:
When a WiFi connection behaves unstable over longer time (eg. long
range), sometimes the user is asked for the password again (the
requester come up already filled), even if it is correct. The request
can come up at any time, depending on the connection quality, and
likely force the user to look up the already correctly entered
password again.
This is very annoying for kiosk-like systems or when using fullscreen
apps.
This bug is stone old and iv'e seens this year by year over a broad
range of Ubuntu versions as well devices (Intel and ARM platform). It
still happens as of Ubuntu 16.04.
So I wonder if this is inevitable by the fact that NetworkManager
sometimes can't decide between an authetication failed by wrong
password vs. authentication failed by bad connection. If not, it
should finally be fixed.
There may be a security problem, for locked down kiosk applications,
as the password may be obtained by kiosk users if the request pops up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633413/+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
