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
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
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
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,
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
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
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
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?
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
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
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
11 matches
Mail list logo
