[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-11 Thread Teunis Peters
well, those running KDE (like me) will still have problems but it should solve 
it for many.
(Lots of reasons, but suffice the gnome shell UI is intensely 
counter-productive for me).  Any chance of it being supported on LTS or disco?

-- 
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/1844422

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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


[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-10 Thread Teunis Peters
re fix committed : does that mean both network-manager and gnome-shell
will be updated as per posted hashes?

-- 
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/1844422

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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


[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-09 Thread Teunis Peters
Fixing PMF would be much higher priority than fixing SAE ;)
it's pretty important that behaves properly.

-- 
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/1844422

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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


[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-09 Thread Teunis Peters
PMF is controlled from AP side over which - mine is always PMF required with 
SAE, for instance, even if it's optional for WPA-PSK on the same SSID.
(that's a configurable option)

PMF should be enabled if at all possible.  PMF optional : mode 1 - recommended 
as long as the driver supports it, and pmf 2 - required - should be the other 
choice.   PMF disabled is only for systems where security is not an issue or 
the driver is known not to function.
It should raise a security alert if PMF is disabled. (eg: warning: this reduces 
security considerably)

-- 
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/1844422

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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


[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

2019-09-28 Thread Teunis Peters
above automated response is correct - it's three backported commits.  There 
should be more before it's done though, so consider this "something to test 
things out".
The network-manager UI does not yet have SAE / WPA3 personal support in this 
backport, and doesn't look like that's available upstream yet - at least not in 
the network-manager git.

-- 
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/1844422

Title:
  WPA3-SAE support

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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


[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

2019-09-28 Thread Teunis Peters
On one side this fixes SAE / WPA3 personal support
on the other, you still can't edit or update WPA3 connections in the GUI 
components.
If you use nmtui or try connecting to WPA3 though, it works.
(I've tested this)

Consider upstream to be "nearing complete"

I've been working on WPA3 support on some AP series so I very much can
test this.  Up until now I've been using manual settings on a custom
compile of wpa_supplicant (etc).

Attached is the backported patches (from networkmanager master, they're not 
even in any tags yet)
I'm going to keep an eye on networkmanager development and follow this report.

However I'd class support as "not yet ready".

** Patch added: "Backport of upstream support"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+attachment/5292389/+files/nm-sae-backport.patch

-- 
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/1844422

Title:
  WPA3-SAE support

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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


[Touch-packages] [Bug 1518526] Re: malware steals resources and is entirely useless

2015-11-21 Thread Teunis Peters
The problem is there's no explanation of why this component is even
present and it behaves a lot like a lot of malware.Otherwise it
seems to be operating a "service" that's a usual path of malware in most
cases.There are no "use" cases, at least that I could find.  The
name's too generic to really work for documentation searches though, and
its readme just says it's a desktop search engine - but not what that is
or why it's useful.

Going to suggest at least putting a "documentation needed" mark on the
software.At least explain why it would be present on a development
machine, for instance, or in a professional office environment where its
behaviour can easily be perceived as a security or confidentiality risk.

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

Title:
  malware steals resources and is entirely useless

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  cannot remove this piece of malware.   It has no use and seems to hijack cpu, 
disk, disk space and in general reduce system to unusable.  Purging the malware 
"tracker-miner-fs" reduces its impact some, but it's still expensive.
  I mean, who uses desktop search tools anyway?   Definitely not someone with 
several thousand source files and no interest in using a desktop to interact 
(that's what console is for).   Definitely not when there's perfectly good app 
menus that (at least used to be) present.

  Please purge this.  Or at least make it possible to purge.   It's malware.
  All "search tools" are malware because they eat disk space like they're the 
only app present and nothing else matters.   They should only ever be optional.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: tracker 1.4.1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Nov 20 21:34:10 2015
  InstallationDate: Installed on 2015-10-14 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1518526/+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


[Touch-packages] [Bug 1518526] [NEW] malware steals resources and is entirely useless

2015-11-20 Thread Teunis Peters
Public bug reported:

cannot remove this piece of malware.   It has no use and seems to hijack cpu, 
disk, disk space and in general reduce system to unusable.  Purging the malware 
"tracker-miner-fs" reduces its impact some, but it's still expensive.
I mean, who uses desktop search tools anyway?   Definitely not someone with 
several thousand source files and no interest in using a desktop to interact 
(that's what console is for).   Definitely not when there's perfectly good app 
menus that (at least used to be) present.

Please purge this.  Or at least make it possible to purge.   It's malware.
All "search tools" are malware because they eat disk space like they're the 
only app present and nothing else matters.   They should only ever be optional.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: tracker 1.4.1-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Nov 20 21:34:10 2015
InstallationDate: Installed on 2015-10-14 (37 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
SourcePackage: tracker
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tracker (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  malware steals resources and is entirely useless

Status in tracker package in Ubuntu:
  New

Bug description:
  cannot remove this piece of malware.   It has no use and seems to hijack cpu, 
disk, disk space and in general reduce system to unusable.  Purging the malware 
"tracker-miner-fs" reduces its impact some, but it's still expensive.
  I mean, who uses desktop search tools anyway?   Definitely not someone with 
several thousand source files and no interest in using a desktop to interact 
(that's what console is for).   Definitely not when there's perfectly good app 
menus that (at least used to be) present.

  Please purge this.  Or at least make it possible to purge.   It's malware.
  All "search tools" are malware because they eat disk space like they're the 
only app present and nothing else matters.   They should only ever be optional.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: tracker 1.4.1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Nov 20 21:34:10 2015
  InstallationDate: Installed on 2015-10-14 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1518526/+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


[Touch-packages] [Bug 1487620] Re: wireless treats driver failure as network security refusal

2015-08-25 Thread Teunis Peters
The being pushed onto the nearest open network is the security risk
part of the bug.

-- 
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/1487620

Title:
  wireless treats driver failure as network security refusal

Status in network-manager package in Ubuntu:
  New

Bug description:
  I've a Lenovo 585 with Broadcom Corporation BCM4313 802.11bgn Wireless 
Network Adapter - this combination leads to frequent driver failures (sudden 
component shutdowns) with sound and network hardware being the most likely to 
temporarily abort.
  (this isn't the first laptop I've seen this problem on either)

  Every time the hardware crashes and resets, network-manager treats
  this as a security abort and asks (erroneously) for network
  credentials.

  a: this disrupts all running program and puts up a modal dialogue
  b: this is unnecessary, because above.
  c: this is a security risk because it will try (under normal circumstances) 
to hop networks until it finds an open one, and this can put the unit into a 
secure vulnerable state.

  I'm happy to help provide more info - this bug hits me anywhere up to
  several times an hour.

  recommend : this is a security risk / serious / blocking (fix asap)
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Aug 21 14:20:55 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-28 (692 days ago)
  InstallationMedia: Linux Mint 15 Olivia - Release amd64 (20130520)
  IpRoute:
   default via 10.253.0.1 dev wlan0  proto static  metric 1024 
   1.1.1.1 via 10.253.0.1 dev wlan0  proto dhcp  metric 10 
   10.253.0.0/16 dev wlan0  proto kernel  scope link  src 10.253.0.20 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2 
 IUGO_STAFF  25f36dd0-8cfa-4336-91a4-2ac49e7c3b4d  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1 
 --  ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0 
 --  ----   
  
   virbr0-nic  tap   unmanaged/org/freedesktop/NetworkManager/Devices/3 
 --  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1487620/+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


[Touch-packages] [Bug 1487620] Re: wireless treats driver failure as network security refusal

2015-08-25 Thread Teunis Peters
Open networks are a direct security risk, at least in some locations.
And that does include the neighbours of my office.It's not
immediately obvious one has been put into a security risk situation if
one is busy working.

There's also no obvious way to mark a network (even if it's visibly a
honey pot for harvesting passwords) as unhealthy/bad, because the above
bug will mean the system automatically connects.

-- 
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/1487620

Title:
  wireless treats driver failure as network security refusal

Status in network-manager package in Ubuntu:
  New

Bug description:
  I've a Lenovo 585 with Broadcom Corporation BCM4313 802.11bgn Wireless 
Network Adapter - this combination leads to frequent driver failures (sudden 
component shutdowns) with sound and network hardware being the most likely to 
temporarily abort.
  (this isn't the first laptop I've seen this problem on either)

  Every time the hardware crashes and resets, network-manager treats
  this as a security abort and asks (erroneously) for network
  credentials.

  a: this disrupts all running program and puts up a modal dialogue
  b: this is unnecessary, because above.
  c: this is a security risk because it will try (under normal circumstances) 
to hop networks until it finds an open one, and this can put the unit into a 
secure vulnerable state.

  I'm happy to help provide more info - this bug hits me anywhere up to
  several times an hour.

  recommend : this is a security risk / serious / blocking (fix asap)
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Aug 21 14:20:55 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-28 (692 days ago)
  InstallationMedia: Linux Mint 15 Olivia - Release amd64 (20130520)
  IpRoute:
   default via 10.253.0.1 dev wlan0  proto static  metric 1024 
   1.1.1.1 via 10.253.0.1 dev wlan0  proto dhcp  metric 10 
   10.253.0.0/16 dev wlan0  proto kernel  scope link  src 10.253.0.20 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2 
 IUGO_STAFF  25f36dd0-8cfa-4336-91a4-2ac49e7c3b4d  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1 
 --  ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0 
 --  ----   
  
   virbr0-nic  tap   unmanaged/org/freedesktop/NetworkManager/Devices/3 
 --  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1487620/+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


[Touch-packages] [Bug 1487620] Re: wireless treats driver failure as network security refusal

2015-08-25 Thread Teunis Peters
However, it blacklisting the active and VALID network because of a
driver fault - that's not a security risk, that's just an ongoing
nightmare.   After it goes through the entire group of valid networks,
that's when it starts hopping onto honeypots, and I can usually catch it
before then.

-- 
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/1487620

Title:
  wireless treats driver failure as network security refusal

Status in network-manager package in Ubuntu:
  New

Bug description:
  I've a Lenovo 585 with Broadcom Corporation BCM4313 802.11bgn Wireless 
Network Adapter - this combination leads to frequent driver failures (sudden 
component shutdowns) with sound and network hardware being the most likely to 
temporarily abort.
  (this isn't the first laptop I've seen this problem on either)

  Every time the hardware crashes and resets, network-manager treats
  this as a security abort and asks (erroneously) for network
  credentials.

  a: this disrupts all running program and puts up a modal dialogue
  b: this is unnecessary, because above.
  c: this is a security risk because it will try (under normal circumstances) 
to hop networks until it finds an open one, and this can put the unit into a 
secure vulnerable state.

  I'm happy to help provide more info - this bug hits me anywhere up to
  several times an hour.

  recommend : this is a security risk / serious / blocking (fix asap)
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Aug 21 14:20:55 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-28 (692 days ago)
  InstallationMedia: Linux Mint 15 Olivia - Release amd64 (20130520)
  IpRoute:
   default via 10.253.0.1 dev wlan0  proto static  metric 1024 
   1.1.1.1 via 10.253.0.1 dev wlan0  proto dhcp  metric 10 
   10.253.0.0/16 dev wlan0  proto kernel  scope link  src 10.253.0.20 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2 
 IUGO_STAFF  25f36dd0-8cfa-4336-91a4-2ac49e7c3b4d  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1 
 --  ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0 
 --  ----   
  
   virbr0-nic  tap   unmanaged/org/freedesktop/NetworkManager/Devices/3 
 --  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1487620/+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