Any hope for PEAP/LEAP authentication?

[GoogleCodeExporter]

I know many of us would love to see some PEAP/LEAP for iPhone, especially 
anyone working at a large company or university...  Is this even possible?

Original issue reported on code.google.com by ecal...@gmail.com on 11 Sep 2007 at 1:02

[GoogleCodeExporter]

AFAIK, and I've only worked with PEAP a little bit, both LEAP and PEAP are
implemented at the tcp layer - there should be no reason why a simple 
authentication
client could not be written for the iphone.  Could you give examples of some 
client
you currently use, and like?

Original comment by lok...@gmail.com on 11 Sep 2007 at 4:45

• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Yeah, I think PEAP is much more common anyways.  Also I have noticed that 
several 
universities in my area offer free wifi with PEAP, which would be awesome for 
the 
iPhone.  The ability to cache PEAP session keys is also pretty essential for 
practical use on iPhone.  I am currently using the Microsoft XP PEAP client for 
PC authentication, but I am sure one exists for the OSX framework.

Original comment by ecal...@gmail.com on 11 Sep 2007 at 5:53

[GoogleCodeExporter]

I found a possible open source 802.1x client here: 
http://open1x.sourceforge.net/

Original comment by ecal...@gmail.com on 11 Sep 2007 at 6:04

[GoogleCodeExporter]

Hi, I'm also very interested in seeing this implemented. My university only 
supports
LEAP for network authentication, which is really lame for all the iphone 
owners.  I
wish I could help dev, but my coding knowledge is limited.

Original comment by delore...@gmail.com on 25 Sep 2007 at 8:18

[GoogleCodeExporter]

802.1x is really important. Please add it to this project.

Original comment by 0mania0c...@gmail.com on 21 Oct 2007 at 10:36

[GoogleCodeExporter]

A couple of comments:

*) 802.1X *is* possible for the iPhone... at least theoretically.

*) 802.1X is done at the frame layer, not the TCP layer.  It requires some 
pretty
direct access to the wireless hardware.

*) Issues that need to be solved to make 802.1X viable:

A native iPhone frame handler (there's already one present in OpenLLDP that 
should do
nicely).

Ability to scan for networks via iPhone Airport APIs, connect to said networks. 
(Most
of this is already possible with the work that has been done here)

Ability to set wireless keys. (this is going to be the tricky part)

Since the Apple Airport APIs are proprietary, it's not a simple matter of 
hooking the
bits up.  Some reverse engineering has to take place.

Is anyone up to reverse engineering the key set routines?  I'm afraid it's 
beyond my
capabilities.

Original comment by nonbroad...@gmail.com on 31 Oct 2007 at 10:56