search

Joshua1909 / eapeak

Automatically exported from code.google.com/p/eapeak
0 stars 0 forks source link

PEAP/EAP-TTLS support a MUST #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What would this new feature accomplish?
LEAP is dying if not already dead PEAP and EAP-TTLS are some of the most common 
implementations of EAP and many do not utilize strong authentication 
(certificate validation) it is imperative for the success of eapeak and wifi 
security as a whole for PEAP support in eapwn and EAPeak as a whole alot of the 
work could be offloaded to FREE-RADIUS-WPE or it could be implemented natively 
i would work on this my self but currently i lack the programming skills also 
is there documentation  for EAPeak (programming wise) that also would be 
helpful for eapeak's growth and adoption

What is the expected output?
a more robust and useful EAPeak

What version of the product are you using? On what operating system?
latest hg release via installer script for backtrack 5 R2

Please provide any additional information below.

Original issue reported on code.google.com by jinwal...@gmail.com on 19 Jul 2012 at 10:05

GoogleCodeExporter commented 9 years ago 
What you are describing would require a semi-custom TLS stack to be designed.  
This is necessary because PEAP, EAP-TLS and EAP-TTLS all require it.  Designing 
a custom TLS stack is not feasible at this time and modifying EAPeak to support 
an available one would require massive modifications.

At this time, this is not a feature that will be actively pursued by the 
project.  Integration at a much later point in time is a possibility.

Original comment by zeroStei...@gmail.com on 15 Aug 2012 at 11:28