On Tue, Dec 9, 2008 at 5:35 AM, Alan DeKok [EMAIL PROTECTED]wrote:
Jason Wittlin-Cohen wrote:
I already do that with the Juniper Access Client. The problem is that
the client certificate has the user's name as the Common Name and that
is sent in the clear. PEAP/EAP-TLS sends the user's
On Tue, Dec 9, 2008 at 5:35 AM, Alan DeKok [EMAIL PROTECTED]wrote:
Jason Wittlin-Cohen wrote:
I already do that with the Juniper Access Client. The problem is that
the client certificate has the user's name as the Common Name and that
is sent in the clear. PEAP/EAP-TLS sends the user's
Ivan,b
I already do that with the Juniper Access Client. The problem is that the
client certificate has the user's name as the Common Name and that is sent
in the clear. PEAP/EAP-TLS sends the user's certificate through the tunnel
obviating the issue. I admit this isn't a large problem but it
http://wiki.freeradius.org/EAP
You should be able to set ananymous as user name for outer tunnel EAP-TLS
negotiation on the supplicant and use EAP-TLS with identity hidden.
Ivan Kalik
Kalik Informatika ISP
Dana 9/12/2008, Jason Wittlin-Cohen [EMAIL PROTECTED] piše:
I'm attempting to setup
Jason Wittlin-Cohen wrote:
I already do that with the Juniper Access Client. The problem is that
the client certificate has the user's name as the Common Name and that
is sent in the clear. PEAP/EAP-TLS sends the user's certificate through
the tunnel obviating the issue. I admit this isn't a
I forgot to mention that I'm running FreeRADIUS 2.1.0 on Ubuntu 8.10
(2.1.0+dfsg-0ubuntu2 to be exact). As the original binary didn't come with
SSL support, I recompiled it using the Ubuntu source package. The client
computer I have been testing run Windows XP SP3.
Jason
--
Jason Wittlin-Cohen
6 matches
Mail list logo
