Philipp Gassmann, this bug was reported a while ago and there hasn't
been any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live
Seems like this currently is being worked on by the Fedora developers:
http://fedoraproject.org/wiki/Features/RealHotspot
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Branch linked: lp:~ubuntu-branches/ubuntu/lucid/network-manager-
applet/lucid-security
** Branch linked: lp:~ubuntu-branches/ubuntu/natty/network-manager-
applet/natty-security
** Branch linked: lp:ubuntu/oneiric-security/network-manager-applet
--
You received this bug notification because y
Joseph, why have you changed the status to Incomplete? Should we report
another bug about the kernel or what additional info do we need? Are
there any upstream kernel bug about this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network
Forgot to add the same bug tag to close the bug with the network-
manager-applet, but it now also contains code to fix adhoc WPA. We can
close this as Fix Released.
** Changed in: network-manager-applet (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification bec
** Branch linked: lp:~network-manager/network-manager/ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905748
Title:
Create WPA2 adhoc is Open, not encrypted
Status in “
This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu1
---
network-manager (0.9.4.0-0ubuntu1) precise; urgency=low
* New upstream release 0.9.4.0: (LP: #960494)
- settings: quiet warning when checking for AdHoc WPA connections
- core: suppress useless log messa
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905748
Title:
Create WPA2 adhoc is Open, not encrypted
Sta
Adding the nm-applet task because we'll be adding code in both NM and
nm-applet to workaround this.
FWIW; it's indeed been broken for a while:
http://thread.gmane.org/gmane.linux.kernel.wireless.general/87543/focus=87554
** Also affects: network-manager-applet (Ubuntu)
Importance: Undecided
I checked the behaviour of previous releases with LiveCDs.
On 11.04 creating a WPA WLAN leads to an open network.
On 10.10 I saw a WEP secured net (in Wifi Analyzer, Android) but the connection
information in Ubuntu said WPA.
I think it's the behaviour or Ubuntu 10.10 which led me to think it
wo
wext fails in a similar way:
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
ioctl[SIOCSIWGENIE]: Operation not supported
wpa_driver_wext_set_psk
Association request to the driver fa
As a note to myself or developers who might be working on the issue:
nl80211: Join IBSS request sent successfully
wpa_driver_nl80211_set_key: ifindex=3 alg=2 addr=0x495e2c key_idx=0 set_tx=1
seq_len=6 key_len=32
nl80211: set_key failed; err=-67 Link has been severed)
Cancelling authentication tim
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905748
Title:
Create WPA2 adhoc is Open, not encrypted
Status in “linux” package in Ubuntu:
I
@mathieu-tl Stock Android does not support ad hoc wlan. See here
http://code.google.com/p/android/issues/detail?id=82 (Second most stars
of all issues there)
There are some custom roms like Cyanogenmod7 that support ad-hoc. And
there are ways to replace wpa_supplicant manually with a version that
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
Using static IP addresses to configure both, they are mutually reachable
which proves they are associating to the same BSSID.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/90574
And the same on a different system, with ath9k (with the "host" using
iwlwifi):
BSS 4e:75:8f:95:91:12 (on wlan0)
TSF: 191896339578 usec (2d, 05:18:16)
freq: 2412
beacon interval: 100
capability: IBSS Privacy (0x0012)
signal: -55.00 dBm
last seen: 288
The above was tested with the simplest form for enabling IBSS/WPA,
inspired from the default wpa_supplicant.conf shipped configuration,
from the upstream tarballs:
mtrudel@gaea ~/Documents % cat wpa-adhoc.conf
ap_scan=2
network={
ssid="test adhoc"
mode=1
frequency=2412
Running wpasupplicant on the command line with debugging logs enabled
shows that it does think it's enabling WPA, even if that doesn't seem to
get done at the kernel level.
** Attachment added: "wpa_adhoc_debugging.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/905748/+att
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevic
Joseph, please define what additional information is needed. As per
above, in Brad's automated comment:
"If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.". I think we've sat
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905748
Title:
Create WPA2 adhoc is Open, not encrypted
Sta
We've been able to reproduce it on multiple drivers: iwlwifi, rt2800pci,
ath9k and iwl4965. I think we can safely say it's reproducible on most
drivers, and thus probably something that needs to be fixed in kernel
code outside of drivers' code.
Philipp; you may still want to run 'apport-collect 90
I installed Ubuntu 11.04 on the same laptop. Creating an adhoc shared
network shows "Open" in Wifi-Analyzer, and "Open" in the wireless
settings. (Although trying to connect fails to get an IP address).
--
You received this bug notification because you are a member of Desktop
Packages, which is s
Philipp; yes, we can rely on that test because Android does support ad-
hoc for WPA. WPA2 is another story ;)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905748
Title:
Crea
I can reproduce this using a laptop with iwl4965, and a Nexus One.
In Wifi-Analyzer, it is displaying as being "WPA" with a lock icon, but
when I go into the wireless settings, it says "Open". I can definitely
connect without a password, and can access the Internet through the
adhoc network.
I ag
@mathieu-tl can you rely on your quick test connecting with android?
Android doesn't support Adhoc per default. With the App Wifi-Analyzer
you can see some details.
When I create an AdHoc and select WPA, it's now recognised as WPA. WPA2
would be better, I guess. But before it was open.
Why is it
This issue is reproducible even without NM, using wpasupplicant directly
to create a adhoc network, and is definitely true on iwlwifi and
rt2800pci; so it deserves to be looked at at the kernel level.
FWIW, I though I had seen it work properly on ath9k, I'll test again
tomorrow to be certain.
In
Even IBSS/RSN seems to either appear as not secured, or fails to be
connected to with a quick test using my android phone; we'll explicitly
disable WPA when creating ad-hoc networks instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This isn't quite done yet because making IBSS/RSN (adhoc with wpa2) the
default instead of WPA with TKIP (as wpa-none) turns out to be a little
more difficult to implement and test than initially expected. So; I'm
still working on this.
** Changed in: network-manager (Ubuntu)
Status: Confir
Yes, please do. Either we fix it to properly set up WPA, or we remove
WPA from the list, but having it display WPA and actually set up
unencrypted is evil.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https:/
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905748
Title:
Create WPA2 adhoc is Open, not encrypted
Indeed, it's borked. This should be set to High considering it's a
security vulnerability; perhaps I'd just go ahead and grey out WPA from
the list if that makes a bit more sense and avoids getting people to
think their ad-hoc is secure when it's not.
--
You received this bug notification because
** Bug watch removed: GNOME Bug Tracker #654772
https://bugzilla.gnome.org/show_bug.cgi?id=654772
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905748
Title:
Create WPA2 a
I've confirmed this in oneiric (0.9.1.90-0ubuntu6) and precise
(0.9.1.90-0ubuntu7).
I glanced at the network-manager-applet code and believe that wpa-none
should be supported for ad-hoc networks. I don't see any obvious fixes
in the upstream git repo, nor any related upstream bugs. However, I did
Can anyone reproduce this bad behaviour?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905748
Title:
Create WPA2 adhoc is Open, not encrypted
Status in “network-manager” pac
** Description changed:
When I create a new network with networkmanager, select wpa2 personal
and enter a password, the network that gets created is actually Open. In
the connection information on Ubuntu, the network ist shown as WPA2
secured, but I can connect with other devices without e
** Attachment added: "The same network in the Connection information from
network-manager"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/905748/+attachment/2637466/+files/network-manager%20wpa2%20open.png
--
You received this bug notification because you are a member of Desk
** Attachment added: "created network on android"
https://bugs.launchpad.net/bugs/905748/+attachment/2637465/+files/screenshot-1324143269201.png
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network
39 matches
Mail list logo
