Bug 289812

Summary:	adhoc wireless security settings
Product:	[Unmaintained] Network Management	Reporter:	Germano Massullo <germano.massullo>
Component:	general	Assignee:	Lamarque V. Souza <lamarque>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	kevin.kofler, rdieter
Priority:	NOR
Version:	0.9
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Germano Massullo 2011-12-25 22:37:06 UTC

Version:           0.9 (using Devel) 
OS:                Linux

If you create a new adhoc network and you set wireless security like WPA, you will not find a secured adhoc wifi connection in wifi list. So the adhoc network will be setted as if you have never setted it as secured.

Reproducible: Always

Steps to Reproduce:
Create a new secured adhoc wifi network

Actual Results:  
The new adhoc wifi network is not secured

Expected Results:  
I expect to be able to share an adhoc SECURED network

The KDE version is 4.7,4 from Fedora 16 stable repo, it does not appear in the version list of bugreport webpage

Comment 1 Lamarque V. Souza 2011-12-25 23:45:58 UTC

How did you test that the connection was not encrypted?

I still do not understand how to reproduce the problem. I can create a shared wifi connection here, with WEP, and it asks for the WEP key. All wifi shared connections are ad-hoc with NetworkManager. NetworkManager does not support WPA with ad-hoc as far as I know.

Comment 2 Germano Massullo 2011-12-25 23:48:32 UTC

You must use WPA encryption.
When older Fedora KDE were using nm-applet, we were able to use wpa in adhoc networks

Comment 3 Lamarque V. Souza 2011-12-26 00:01:57 UTC

How do you create shared connections in nm-applet. There is no option here to do it.

Comment 4 Lamarque V. Souza 2011-12-26 00:07:59 UTC

You also have not answered my question about how you are testing if the connection is encrypted or not.

Comment 5 Lamarque V. Souza 2011-12-26 02:52:49 UTC

Git commit bea4e19700f0c345929559875345699a2a0ef9ba by Lamarque V. Souza.
Committed on 26/12/2011 at 02:57.
Pushed by lvsouza into branch 'master'.

Only enable wifi security methods None, WEP and WPA/WPA2 Personnal for
ad-hoc connections. NM does not support the other methods when on ad-hoc
mode.
Related: bug 289812

M  +2    -2    libs/internals/wirelesssecurityidentifier.cpp
M  +1    -1    libs/ui/security/wirelesssecuritysettingwidget.cpp

http://commits.kde.org/networkmanagement/bea4e19700f0c345929559875345699a2a0ef9ba

Comment 6 Lamarque V. Souza 2011-12-26 02:52:50 UTC

Git commit e14f5841d6261f81334e0d3c220588036ef599b2 by Lamarque V. Souza.
Committed on 26/12/2011 at 03:51.
Pushed by lvsouza into branch 'master'.

Configure adhoc WPA wifi like nm-applet does.
Related: bug 289812

M  +1    -0    backends/NetworkManager/settings/802-11-wireless-securitydbus.cpp
M  +8    -1    libs/ui/security/wirelesssecuritysettingwidget.cpp

http://commits.kde.org/networkmanagement/e14f5841d6261f81334e0d3c220588036ef599b2

Comment 7 Lamarque V. Souza 2011-12-26 03:00:13 UTC

Git commit cd59fd5850aa50461674907d8873b4566dbc1cc1 by Lamarque V. Souza.
Committed on 26/12/2011 at 02:57.
Pushed by lvsouza into branch 'nm09'.

Only enable wifi security methods None, WEP and WPA/WPA2 Personnal for
ad-hoc connections. NM does not support the other methods when on ad-hoc
mode.
Related: bug 289812

M  +2    -2    libs/internals/wirelesssecurityidentifier.cpp
M  +1    -2    libs/ui/security/wirelesssecuritysettingwidget.cpp

http://commits.kde.org/networkmanagement/cd59fd5850aa50461674907d8873b4566dbc1cc1

Comment 8 Lamarque V. Souza 2011-12-26 03:18:03 UTC

Please test if the commits above fix your problem.

Comment 9 Germano Massullo 2011-12-27 21:18:28 UTC

> How did you test that the connection was not encrypted?
> 
> I still do not understand how to reproduce the problem. I can create a shared
> wifi connection here, with WEP, and it asks for the WEP key. All wifi shared
> connections are ad-hoc with NetworkManager. NetworkManager does not support WPA
> with ad-hoc as far as I know.
I tested using another computer to see if the adhoc network is protected or not.
I don't consider WEP encryption because it is faster to crack it instead to entering the password.


Rex Dieter from Fedora built the following packages using your patch
http://koji.fedoraproject.org/koji/taskinfo?taskID=3607010
Things did not change, the problem is identical as before

Comment 10 Lamarque V. Souza 2011-12-27 21:32:57 UTC

It was not only one patch that I commited to fix this problem. It were four in total: bea4e19700f0c345929559875345699a2a0ef9ba , 1a951cb902da615cb83899ce84a5cf7caf71920c , e14f5841d6261f81334e0d3c220588036ef599b2 and 1cfda04aa1e7adf066c52c0a08191e9244e06308

The configuration created here is almost equal to what nm-applet creates. The only differences is that Plasma NM does not enable IPv6 by default, does not mark the connection as auto-connect, does not mark it as system connection by default and do not fix the wifi card MAC. I think those are not necessary to make it work.

Anyway, even creating the connection with nm-applet my Windows XP (in my second notebook) and my cellpho were not able to connect to my first notebook.

Are you sure this is not broken in NM 0.9.2?

Comment 11 Kevin Kofler 2011-12-27 22:42:05 UTC

We (well, Rex Dieter, really) packaged a new snapshot, i.e. we included all the relevant commits, not just one.

Comment 12 Germano Massullo 2011-12-28 23:25:13 UTC

Well, I have some important news: I downloaded a livecd of Fedora 16 Gnome and, if you enable a wep hotspot everything is okay, if you enable a wpa hotspot, the hotspot computer tells you that your adhoc network in secured, instead it is not secured! I connected to that wifi network with my android phone without entering a passphrase.
So it is defenitely a NetworkManager bug.

I am going to close the bugreport as upstream