[plasma-nm] [Bug 369069] [RFE] Change how a new wireless connection is configured.
https://bugs.kde.org/show_bug.cgi?id=369069 Jan Grulich changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #7 from Jan Grulich --- This is NM's default configuration and I'm not going against it. If the default configuration changes in NM then we can change it on our side as well. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 369069] [RFE] Change how a new wireless connection is configured.
https://bugs.kde.org/show_bug.cgi?id=369069 --- Comment #6 from kdde@porcupinefactory.org --- I have no idea how I didn't notice that before. That solves the configuration workflow I suppose. I still claim that the MAC default is unsuitable for a user unaware of WiFi privacy problems. As the defaults author makes decisions on behalf of non-specialists, the defaults should be safe and conservative. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 369069] [RFE] Change how a new wireless connection is configured.
https://bugs.kde.org/show_bug.cgi?id=369069 --- Comment #5 from Jan Grulich --- The editor actually suggests you a list with all visible wireless networks (including signal strength and list of BSSIDs). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 369069] [RFE] Change how a new wireless connection is configured.
https://bugs.kde.org/show_bug.cgi?id=369069 --- Comment #4 from kdde@porcupinefactory.org --- I tend to agree, except for two things. First, creating a new connection manually is (surprisingly) difficult. The nm applet provides no way to copy the SSID, and the new connection editor doesn't allow to select the visible ones either. One would have to scan networks using command line (and it's not obvious how to do it) and copy the SSID from there. Second (this may be a separate problem), I can't see any upsides of using real MAC on hardware that supports changing it. As a consequence, the non-technical user will not know that the software gives away some identifying information about them, and that they have a choice for not disclosing the information by using random MAC. Given that there is no convenient graphical tool for technical users, I don't think it's unreasonable to target the technical ones to some extent. Perhaps attacking the user with a full dialog is a bad idea, but clicking the network name already shows very technical information. Perhaps that's an area that could be used to let the user indicate the need to configure network before connecting? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 369069] [RFE] Change how a new wireless connection is configured.
https://bugs.kde.org/show_bug.cgi?id=369069 --- Comment #3 from Jan Grulich --- Given that we primary target for non-technical users (at least with the applet), I don't think that displaying a configuration with stuff they know nothing about once they try to connect to a wireless network would be more or less confusing for them. For technical users like you I don't think it's a big deal opening the editor and create a connection with configuration you desire. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 369069] [RFE] Change how a new wireless connection is configured.
https://bugs.kde.org/show_bug.cgi?id=369069 --- Comment #2 from kdde@porcupinefactory.org --- The problem with disclosing the real MAC address at "untrusted" locations - even if visited frequently - still exists regardless of traveling. I believe NetworkManager already has something in the works here. The traveling use case will be familiar to anyone who goes abroad. The open networks are plentiful, but a lot of them require (mobile) registration/payment, and foreign names are not always clear, therefore it's not possible to find a good network at first try. You mentioned that the period of inconvenience is short, but it is also critical, because in the traveling network use case the computer would be on battery power and internet access needed ASAP. Granted, I am not sure how many people use a computer on the go these days. Perhaps there doesn't exist a "one size fits all" solution, but I believe that the travelling use case is still valid (if niche). Therefore, it would make everyone happy if on first connection, the password dialog was replaced with the actual connection dialog. This would solve: - the inverted workflow (configure after connecting is bad) - privacy issues (user can choose to randomize MAC before connecting) - travelling use case - custom network configuration -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 369069] [RFE] Change how a new wireless connection is configured.
https://bugs.kde.org/show_bug.cgi?id=369069 --- Comment #1 from Jan Grulich --- Option such as "only reconnect to the same SSID" is probably equal to disabling autoconnect for every other wireless network and NetworkManager doesn't support anthing likke that, thus we cannot support this in our applet. Also a scenario where you need to find any working/free wireless network by trying them one by one is something I wouldn't consider as a valid use case. It's a thing you probably do occasionally when traveling or something like that and the period you would be having problems with using random unsecured wireless network is rather short then something what would bother your for a long time. -- You are receiving this mail because: You are watching all bug changes.
