Thread
:
N900 most annoying bug (to me)
View Single Post
fedor
2010-07-29 , 10:24
Posts: 14 | Thanked: 5 times | Joined on Jun 2010
#
1
In my opinion N900 is an advanced device dedicated to multimedia and connectivity. As such, I expect a lot from n900 business connectivity features.
I work in a complex network environment where wifi connectivity is based on WPA-Enterprise (using eap-tls).
Well, I cannot connect to a wifi network that is protected by wpa-enterprise using eap-tls authentication along with a certificate signed by a private CA.
I read a lot of discussions about this matter but I have never found a useful hint.
I have analyzed n900 logs and even captured the network traffic between n900 and the access point.
In the logs I found errors about some certificates not recognized by available ca (maybe the private CA is not recognized?). If I leave the option “Require client authentication” disabled, the phone doesn't even pass the client certificate when it is requested to do that, resulting in a failed authentication error from eap server. If I enable the option “Require client authentication” than the n900 responds with an error to eap server during tls negotiation (warning: bad certificate).
Of course, the user certificate has been installed on n900 and, of course, the same certificate along with others parameters is perfectly working in a linux laptop with wpa_supplicant running.
What can I do?
Quote & Reply
|
fedor
View Public Profile
Send a private message to fedor
Find all posts by fedor