** Changed in: openssl
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications about this bug
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=798187.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: wpa (Debian)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications
** Changed in: openssl (Ubuntu)
Status: Incomplete = Invalid
** Changed in: openssl (Ubuntu Precise)
Status: Fix Committed = Invalid
** Tags removed: verification-done-precise
** This bug is no longer a duplicate of bug 1104476
Network manager cannot connect to
** Package changed: openssl (Debian) = wpa (Debian)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications about this bug
** Bug watch removed: Email to rt@openssl #
mailto:r...@openssl.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
*** This bug is a duplicate of bug 1104476 ***
https://bugs.launchpad.net/bugs/1104476
** This bug has been marked a duplicate of bug 1104476
Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without
CA_Certificate
--
You received this bug notification because you are a
Finaly found that deleting the WLANs file in /etc/NetworkManager/system-
connections/ solved the problem. Also
http://askubuntu.com/questions/285234/cannot-connect-to-wpa2-wpa-
enterprise-peap-and-mschap?answertab=votes#tab-top gave the right hint.
--
You received this bug notification because
While using ubuntu 12.10 (wpasupplicant 1.0-2ubuntu5 and openssl 1.0.1c-
3ubuntu2) I can login to my company's wireless lan.
But which packages for 13.04 will have that fix which came with
1.0-2ubuntu5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm still having this problem. I've had it now on several different
computers, including now my Lenovo X121e.
For a while, I could login to WPA2-Enterprise wifi, but now I can't: not
eduroam, or any other.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I should add, I'm using Xubuntu 12.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications about this bug go to:
We just implemented a lot Aruba (ap-105) access points and I (we) also
experience this problem (as described @Impact) . While searching the
www I couldn't really pinpoint what I could do as a work-around. I
myself use 12.04, but the problem also exists on 13.04. I have a
Thinkpad T410s. With the
For what it's worth, I'm having this in an up-to-date 12.04 too.
Wireless works flawlessly, except when connecting to an eduroam network,
in which case it times out with this repeated in the syslog:
Apr 17 12:10:49 X kernel: [ 1987.661492] rtl8192c_common: Loading firmware file
I am experiencing this issue on ubuntu 12.10. I am connecting to a an
eduroam wireless network with WPA2 enterprise encryption and the
connection fails after a few minutes. Sometimes it does not connect at
all. Most of the times one of the following work arounds works but the
effect is only
** Changed in: oem-priority/precise
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
The user todaioan seems to be vandalizing a lot of bugs. I'm reverting
his change.
** Changed in: openssl (Ubuntu)
Status: Fix Released = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I wonder this isn't fixed yet. There are many users waitin for a fix,
especially students and profs, because many of them are using the
eduroam network (mentioned some times before).
When using eduroam wifi after a while my notebook stops working like
expected: I'm unable to suspend (kernel
Felix, this bug *has* been fixed in Ubuntu 12.04 (Precise Pangolin) and
later. From your comment, it sounds like you are describing an unrelated
wifi bug. This bug prevented users from connecting to certain WPA2
Enterprise networks. The bug in your comment allows you to connect to a
WPA2
alan_a...@yahoo.com
** Changed in: openssl (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise
@felixhaller: I share your frustration. I have what seems to be yet a
different version of the bug, where in 12.04 I remain unable to connect
to WPA2 Enterprise networks.
The fix for me was upgrading to 12.10. Now I can connect reliably and
maintain the connection. I realize this may not be
I already use 12.10. I can connect to all wifi networks, there are only
problems when connecting to eduroam network (wpa2 enterprise). My
notebook is working just fine with the other networks (eg. my private
one -- WPA2 personal).
I think I will open a new bug...thanks for all the information.
** Changed in: oem-priority
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
My enthusiasm for reporting the problem fixed (#125) was premature: the
connection only worked twice, it is now only able to connect
approximately once in every five attempts. The problem only persists
with the network using WPA Enterprise with AES encryption, a separate
network that uses WPA
I have an ignorant question: There is no AES choice in the configuration
dialog for WPA2, so which of the encryption methods are AES? (Is PEAP
the same as AES?)
Another question: My android (ICS) phone connects successfully to our
wpa2 network using peap, but it automatically configured none for
Fix only alleviated the situation for me. Went from no connectivity to
frequent disconnects. Upgrading to kernel 3.5.0-030500-generic finally
ended months of misery :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
marking verification-done based on comment #125
** Tags removed: verification-needed
** Tags added: verification-done verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
** Changed in: oem-priority
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
For people still having problems (that had problems prior to this
version), please file a new bug referencing this one. Regressions from
the released version with this update should be reported here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package wpasupplicant - 0.7.3-6ubuntu2.1
---
wpasupplicant (0.7.3-6ubuntu2.1) precise-proposed; urgency=low
* debian/patches/session-ticket.patch: disable the TLS Session Ticket
extension to fix auth with 802.1x PEAP on some hardware. (LP: #969343)
--
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/wpasupplicant
/precise-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To
The precise-proposed fix worked for me today at Durham University, UK.
The uni uses WPA2 Enterprise with AES. Thanks to everyone who worked on
the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here in UCSD. No success. Can anyone tell me what versions of stuff you are
using? I am using:
wpasupplicant : 0.7.3-6ubuntu2.1
libssl1.0.0 : 1.0.1-4ubuntu5.5
openssl : 1.0.1-4ubuntu5.5
my kernel is 3.2.0-31-generic
Thanks!
--
You received this bug notification because you are a member of
I can confirm the proposed fix works for me accessing Wifi with
Enterprise security and TTL/PAP authentication.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA
@gllyons the proposed fix also worked for me at Northwestern.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications
rmcd: the tag change was fine, but this bug is special in that it
affects others (people using Aruba) and seems to fix the issue properly.
I suggest asking them to check authentication logs to see what the AP or
authentication server wrote when you tried to connect and did you first
successful
The bug is not fixed on my network (KULeuven/Eduroam)
Dmesg log: (grepped for wlan0)
[ 37.885705] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 103.898976] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 182.706388] wlan0: authenticate with 00:26:99:99:93:cd (try 1)
[ 182.709876] wlan0:
At another location Eduroam works just fine. (BTW: I rebooted my laptop)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
I m also at Northwestern like rmcd but the package in precise-
proposed works fine for me. The proble was first resolved for me in
the package in PPA https://launchpad.net/~mathieu-tl/+archive/sru-
staging ?
But I switched to the one in proposed to see if there was an issue and I
can't find
When switching versions, are you guys making sure to reboot, or at
least kill the wpa_supplicant process?
If you're not, you're still testing the version from before you
upgraded, not the new one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I rebooted after installing the package from proposed and after that I
tried disconnecting and reconnecting a few times to test things and it
all worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@nickurak: Yes, I reboot when I switch versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications about this bug go
Unfortunately, the fix does not work for me. First, to be sure I'm using
the correct version, 'dpkg -l | grep wpa' gives this:
ii wpagui 0.7.3-6ubuntu2.1
graphical user interface for wpa_supplicant
ii wpasupplicant
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
rmcd,
Are you sure that the configuration is correct in NetworkManager, and
that the device is actually allowed to connect?
This works properly for other people, it would be nice to know exactly
what is missing here if anything.
This is all the more important since status 17 is
Actually, 802.11-2007 defines status 17 as Association denied because
AP is unable to handle additional associated STAs -- The API might be
overloaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried the updated wpa program and I still can't access my work
wireless network.
I am using Dell XPS 13 and my company is using Aruba AP.
I saw this in the dmesg:
2985 [130380.278223] wlan0: Wrong control channel in association response:
configured center-freq: 5200 hti-cfreq: 5805
Mathieu,
First, sorry if I was premature in changing the tag, I thought I was
acting as instructed.
I definitely do have permission to access the resource, and my android
phone has no problem connecting. My computer did connect when I first
rebooted, so I presume that serves as a test about
Hi,
I saw a lot of people still having the connection issues after applying
this updates. I don't know if this is caused by a combination of using
Dell XPS 13 + Aruba AP.
I have filed a bug 1019081 to track this issue, so please speak up there
if you are seeing the same problem. I assume this is
Hello rmcd, or anyone else affected,
Accepted into precise-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use
Err, this is *not* in precise-proposed yet as far as I can tell.
Shouldn't be marked as Fix Committed until then.
** Changed in: wpasupplicant (Ubuntu Precise)
Status: Fix Committed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Jeremy, what kind of settings in wpa, if any, make the connection
successful for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To
** Changed in: wpasupplicant (Ubuntu Precise)
Status: Triaged = Fix Committed
** Changed in: oem-priority/precise
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I verified Mathieu's SRU is working very well with a clean precise installation.
I could connect to WPA/WPA2 enterprise network, with a TPLink TL-WR941ND access
point.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
It's quite possible that there are still existing issues and that the
fix in -proposed does not fix the problem for everone. However, due to
the nature of the problem, we will be pushing out the fix in -proposed
anyway, since it fixes the problem for a good number of users. In fact,
it fixes the
I'm wondering if, as rmcd suggests, we're dealing with two separate
bugs (buggy implementations of WPA access points) here. On one hand,
the patch du jour that disables TLS session tickets seems to fix the
problem I've been having authenticating to certain Aruba access points.
On the other hand,
I have a question
This is not a forum for Android but i have android 4.1 and i cannot
connect to wpa either. It could be the same problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Yes the same problem exists on android and it is basiclly the same bug.
Here is the tracking for that
http://code.google.com/p/android/issues/detail?id=34212
Keep in mind that even once a fix is released in android it will still
be necessary for your device maker to make their own patch.
** Bug
Hi Benjamin,
I am using dell xps 13 with precise and my company is using Aruba AP,
which I am not able to connect to it through WPA2 enterprise.
And I don't see libssl1.0.0_1.0.0e-2ubuntu4 in synaptic package
manager anymore. So I am running libssl1.0.0_1.0.1-4ubuntu5.5.
I am using wpagui and
This issue has gotten the attention of our network folks because of the
similar Android Jelly Bean problem. Would it help for affected folks to
provide more details about their network configurations? In addition to
using Aruba networks, we have a steel-belted Radius authentication
server. That
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications about this bug go to:
Sadly, I still seem to be hitting this issue under quantal. Downgrading
openssl libraries to 1.0.0e-2 (as in an earlier comment) resolved the
problem. So I think marking this Fix Released for wpa may be
premature.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Oh, and a co-worker is still hitting the problem with the version
recently released to precise-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA
No longer needs to be tracked by the release team for Q (since it's Fix
Released via the upload of wpa above); so I'm removing the
rls-q-incoming tag.
Also unassigning Colin and marking the openssl tasks Incomplete; so far
there isn't any indication that it needs extra work for openssl, and
** Description changed:
+ [Impact]
+ Breaks 802.1x (PEAP) authentication for wireless networks using specific
authentication servers and/or AP hardware. Aruba network devices specifically
are known to be affected; and is a popular device type used in enterprises to
secure wireless networks.
+
Uploaded wpasupplicant 0.7.3-6ubuntu2.1 to precise-proposed; waiting to
be reviewed by the SRU team.
Note: this fix is already in Quantal, but the source package is now
called wpa rather than wpasupplicant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: oem-priority/precise
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
Hi,
Am I correct in assuming that this'll show up in Precise, too?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
** Branch linked: lp:ubuntu/wpa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications about this bug go to:
The fix is now in Quantal:
wpa (1.0-2ubuntu5) quantal; urgency=low
* debian/patches/session-ticket.patch: disable the TLS Session Ticket
extension to fix auth with 802.1x PEAP on some hardware. (LP: #969343)
I also updated the tasks to note that the fix in quantal is on the 'wpa'
source
Preparing the upload for Quantal now...
** Changed in: wpasupplicant (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to
Good point @rmcd1024, I too am using 0.7.3-6ubuntu2.1~mtrudel1
One of my campus network support staff contacted me hoping that this bug
had a general solution released.
So what kind of additional testing do we need to do before this patch
can be moved out of a PPA and into the main distribution?
No additional testing to go through the SRU process (which means another
package, in precise-proposed, and a testing period of at least 7 days).
I'll get to this in a few hours :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@mathieu-tl: I think you're correct. As a test, I rebooted into ubunutu
11.10. In the past, I have always been able to connect with 11.10, this
time I again got connection denied with reason 17. However, my Android
phone connects immediately to the same AP, so I don't think the AP is
overloaded.
The version in http://ppa.launchpad.net/mathieu-tl/sru-staging/ubuntu
worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To
Just to clarify, I'm using (and unable to connect with
0.7.3-6ubuntu2.1~mtrudel1, which I believe is the version Diane Trout is
referring to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
rcmd: the issues you're seeing are related to roaming, and not that
patch (or at least, not without any doubt). What reason 17 means is
that the AP can't handle new stations; which probably means it's
overloaded.
FWIW, I can always add the extra other setting
I can confirm that the patch mentioned in #72 works for me on Arch Linux
(patch here: http://w1.fi/bugz/show_bug.cgi?id=447).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to
I appear to have the same issue. Connecting to WPA2-enterprise network fails on
ubuntu 12.04 but succeeds on 11.10 using identical settings.
System:
Dell Latitutude E5500
Internal Wireless card
Settings:
WPA2-enterprise
PEAP
no certificate (ignored certificate warning)
DHCP assigned address and
** Changed in: openssl (Debian)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage notifications
@DianeTrout: I was finally able to get a wireshark capture of an
unsuccessful connection attempt (thanks for your help Diane!), and I can
confirm that unknown 15 is present in the Client Hello handshake
protocol.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Branch linked: lp:~mathieu-tl/ubuntu/precise/wpasupplicant/session-
ticket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA enterprise wireless
To manage
Not being able to keep a stable connection is a different issue than not
being able to connect at all -- please file your own separate bug report
if you're running into such issues.
As far as I could tell, in most cases disabling the Session Ticket
extension allowed wpasupplicant to auth to the
Swapped to the packages from Mathieu's PPA. Connects like a charm where
the stock packages fail. Long term connection stability not tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Mathieu's ppa did not work for me. (To be clear, I only installed the
package wpasupplicant_0.7.3-6ubuntu2.1~mtrudel1.) I get a long string of
these:
[ 25.748578] wlan0: authenticate with d8:c7:c8:71:xx:yy (try 1)
[ 25.946467] wlan0: authenticate with d8:c7:c8:71:xx:yy (try 2)
[ 25.947192]
Mathieu's PPA wpasupplicant does allow for a successful authentication.
Unfortunately, as soon as I roam to a different AP the connection dies
and won't join again until I turn wifi off and back on. See attachment
for the log during roam.
** Attachment added: syslog_wifiroam.txt
Like rmcd1024 the patched wpasupplicant from Mathieu did not help me. The
behavior is
still the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA
I just tested xubuntu 12.10 Alpha three and it did *not* connect. I get
the same sslv3 alert bad certificate error.
Here is what I was told about our recent networking change: we were
using Cisco WAPs, whereas now we're using Aruba. In both cases, we used
WPA2 Enterprise MSCHAPv2 PEAP for the
I tested the patch in the wpa supplicant ticket, but while it allows me
to actually connect does not provide for a stable connection. I've
reverted back to the official package for now, but the inability to join
my work wireless is becoming more painful.
Just like the original poster, I have an
@rcmd Could you try running a packet sniffer (like wireshark)?
For me this bug shows up when my client hello message includes an
Unknown 15 extension. One of the other patches that worked for some
people disabled the SessionTicket extension. The upstream bug report was
wondering if it was all
I also tested last night with the latest libssl installed on 12.04
libssl-1.0.1-4Ubuntu5.3, and the wireless connection disconnected after
about 5 minutes of usage as before. This is a major issue, and means I
have had to move back to 11.10 just to connect wirelessly.
As 12.04 is an LTS, it does
Well tested this evening with 12.10 Alpha three , which has the
following versions intalled , and it works fine
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.5.0-6-generic #6-Ubuntu SMP Mon Jul 23 19:52:14 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ dpkg -l | grep libssl
ii
Diane Trout's wpa-supplicant gnutls patch has stopped working. My
institution has made some changes in their wireless configuration. I
haven't been able to find out what they did, and it's possible that some
other software upgrade on my system caused the problem instead.
In any event I am now
Disabling the TLS heartbeat in openssl does *not* work for me. However,
disabling TLS session tickets in wpa_supplicant does. See the wpa bug
report for a patch. http://w1.fi/bugz/show_bug.cgi?id=447
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I tried the version of openssl lp:ubuntu/openssl revno: 80 tags:
1.0.1-4ubuntu4 but that version's changelog didn't seem to refer to Bug
#1020621, so I tried debian's 1.0.1c-3 which did refer to including a
fix for their version of the Bug #1020621 bug debbugs #675990.
Unfortunately neither
One thing my wireshark captures were showing me, is that the more recent
versions of openssl were adding an extension 15. I tracked that down
as the tls heartbeat extension. Using debian's 1.0.1c package I
prevented openssl from adding the Heartbeat extension to the client
hello message, and
The attachment disable heartbeat. of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'patch'
Tested this last night and seeing exactly the same issues on a machine with a
very similar Centrino WIFI adapter as the original poster.
Test with these versions Openssl 1.0.1-4ubuntu5 and wpasupplicant_0.7.3 on
Ubuntu 12.04 - fully patched as of 10/07/2012 with proposed sources selected.
I
Does this lastest openssl fix this bug:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1020621
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969343
Title:
Unable to connect to WPA
@cement_head: If you're asking whether 1.0.1-4ubuntu5.3 (from precise-
proposed) fixes the WPA Enterprise problem, the answer is no, at least
for me. I replaced Diane Trout's wpasupplicant with
wpasupplicant_0.7.3-6ubuntu2_amd64.deb and remained unable to connect.
Once I put her version back,
Neo: what you're seeing is a different issue -- please file a new bug
report for it.
It's indeed not likely that switching wpasupplicant to use gnutls
instead of OpenSSL will actually fix the bug (or it will, but introduce
others). In any case, it's not the kind of change I'm prepared to do as
a
1 - 100 of 179 matches
Mail list logo
