After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613071 - Wi-Fi Protected Setup (WPS)
Wi-Fi Protected Setup (WPS)
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Lubomir Rintel
NetworkManager maintainer(s)
Depends on:
Blocks: 694819
 
 
Reported: 2010-03-16 19:17 UTC by Thomas Creutz
Modified: 2020-11-13 12:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas Creutz 2010-03-16 19:17:39 UTC
It will be nice to see WPS support in NetworkManager.
WPS is supported by wpa_supllicant and dbus interface should be ready, read: 

http://lists.shmoo.com/pipermail/hostap/2009-April/019634.html

What is the state in NM? I found only this: http://osdir.com/ml/networkmanager-list/2010-01/msg00262.html

Regards,
Thomas
Comment 1 Dan Williams 2010-10-06 20:56:36 UTC
Yes, we do need this in NM.  Its currently blocking on updating NM to work with the new DBus interface that wpa_supplicant 0.7 and later expose.  I've just pushed an initial round of work for that to the 'sup-rework' branch but that's only about 1/4 of the work required.  We'd also need some changes to the GUI bits to accept a one-time PIN code for WPS instead of the passphrase, and then also some mechanism to get the passphrase back to the user-settings service when we finally get that from the supplicant.
Comment 2 Bruno Bigras 2011-08-07 13:57:14 UTC
(In reply to comment #1)
> Yes, we do need this in NM.  Its currently blocking on updating NM to work with
> the new DBus interface that wpa_supplicant 0.7 and later expose.  I've just
> pushed an initial round of work for that to the 'sup-rework' branch but that's
> only about 1/4 of the work required.  We'd also need some changes to the GUI
> bits to accept a one-time PIN code for WPS instead of the passphrase, and then
> also some mechanism to get the passphrase back to the user-settings service
> when we finally get that from the supplicant.

Any progress on this?
Comment 3 Martin Jürgens 2013-06-17 15:19:45 UTC
Any chance that this gets implemented in the future? The DBus problem  should be sorted out by now, shouldn't it?
Comment 4 Konstantin Svist 2015-07-27 01:57:14 UTC
Ping
Many routers support this nowadays (nevermind that it's poor security for the router; users in a public location -- e.g. cafe -- want to connect)
Comment 5 Marco Balmer 2016-07-22 05:51:16 UTC
+1
Thanks for an update and status about this bug.
Comment 6 bam 2016-07-30 15:52:14 UTC
Any progress on this?
Comment 7 André Klapper 2016-07-30 16:10:39 UTC
Looks like someone was experimenting with adding support, see https://mail.gnome.org/archives/networkmanager-list/2015-August/msg00024.html

Potential workaround: https://www.corsac.net/?rub=blog&post=1576
Comment 8 c.buhtz 2016-12-25 15:53:33 UTC
What is the status currently?

WPS is standard today and used a lot. It is very important for NM to support this because it brings linux near to a usable and ergonomic "desktop linux".
Comment 9 André Klapper 2016-12-26 17:48:02 UTC
@c.buhtz: Please avoid adding advocacy "+1" comments that do not add anything new or relevant to the *technical* discussion. Thank you! :)
Comment 10 c.buhtz 2016-12-26 20:05:06 UTC
@klapper: I described why this feauter is usefull. Are you not interested in the comments and views of your users?! You think this is "anything new"?
Comment 11 André Klapper 2016-12-27 07:30:55 UTC
(In reply to c.buhtz from comment #10)
> @klapper: I described why this feauter is usefull. 

...and we all know already why it is useful.

> Are you not interested in the comments and views of your users?! 

Comments that only repeat previous comments are not welcome. They only create notifications that someone needs to read. Thanks for your understanding.
Comment 12 Lubomir Rintel 2017-04-15 08:03:44 UTC
In review at bug #781336

Only the PBC setup works now.

Supporting PIN method needs some work; especially a new secret property to hold the PIN and request it from the agents. Notably, hostapd doesn't seem to support it w/o an external registar, so I can't really test it. I have no idea how popular is the PIN method.
Comment 13 Lubomir Rintel 2017-04-15 11:30:28 UTC
(In reply to Lubomir Rintel from comment #12)
> In review at bug #781336
> 
> Only the PBC setup works now.
> 
> Supporting PIN method needs some work; especially a new secret property to
> hold the PIN and request it from the agents. Notably, hostapd doesn't seem
> to support it w/o an external registar, so I can't really test it. I have no
> idea how popular is the PIN method.

The PIN method now works too. Turns out hostapd actually does support the PIN method only my stubornly crashy Wi-Fi firmware was unhappy.
Comment 14 gnutter 2018-05-14 12:13:08 UTC
" They only create notifications that someone needs to read. "

Well this bug was reported on 2010 and remains unresolved. Maybe someone needs to be reading notifications that this is an ever more pressing problem not a ten year old dead issue. 

Thanks for your understanding.
Comment 15 Thomas Creutz 2018-10-19 19:03:49 UTC
"pressing" problem < how funny - it matches the topic really fine :D

we all only want to "press" this button for that long time.

Joking - I also dont unterstand why the developend stopped - it was all so promising that Lubomir was working on it? Hope he is still ok.
Comment 16 André Klapper 2020-11-12 14:25:46 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).
Comment 17 bam 2020-11-13 12:09:27 UTC
Thomas, would you file it on Gitlab please?
If not I'll do it for myself.
Comment 18 Thomas Haller 2020-11-13 12:23:55 UTC
(In reply to bam from comment #17)
> Thomas, would you file it on Gitlab please?
> If not I'll do it for myself.

what do you think is missing?

This bug is about WPS support in general. That was added a few years ago.

If something doesn't work (or does not work well), it warrants a bug report. But then it also requires information beyond what was discussed in this bugzilla, because those things are done.

I change the RESOLVED state from OVSOLETE to FIXED, because the inital problem was addressed -- even if you think that the current solution is not satisfactory, but then please report the further details as a new issue.

Thanks!