Make eapeak working with Scapy 2.2.0

[GoogleCodeExporter]

Hello, when I run eapeak I get message:

Error: Missing Scapy Libraries, Please Install Scapy From The Community 
Repository
Error: Version Must Be >= 1538:d80170e42ced
Error: Now Exiting...

I believe it is because old version of scapy library didn't implement EAP() and 
EAPOL() structures. These structures were implemented only in dev version. But 
nowadays, scapy is in version 2.2.0 and implements these structures out of the 
box. Could you please update this great to make it work with new versions of 
scapy included in most linux distros?

Original issue reported on code.google.com by antal.lu...@gmail.com on 4 Sep 2013 at 1:55

[GoogleCodeExporter]

I'll take a look. 

Original comment by zeroStei...@gmail.com on 20 Sep 2013 at 1:47

[GoogleCodeExporter]

Scapy 2.2.0 was released February 28th, 2011 and it did include EAP and EAPOL 
layers (see http://hg.secdev.org/scapy/rev/74274bb47d3c).  This is not enough 
for eapeak to function properly however.  Starting in February 2011 I started 
to add the expanded EAP layers necessary for EAPeak to function, including 
EAP_TLS, EAP_TTLS, PEAP, and EAP_Fast (see 
http://hg.secdev.org/scapy-com/log?rev=Spencer+McIntyre).

Unfortunately at this time the main trunk of Scapy version 2.2.0 does not 
include these additional layers which are necessary.  Because of this EAPeak 
still requires you to install Scapy from the community repository.

I've been meaning to include the additional layers in a separate file to fail 
over to but I haven't gotten around to doing it yet.

Original comment by zeroStei...@gmail.com on 24 Sep 2013 at 2:35

[GoogleCodeExporter]

I looked into supporting the core version of Scapy.  The problem is that 2.2.0 
is so far behind the community branch that alot of fields and layers are 
different or missing (XThreeBytesField, UTCTimeField, FieldThreeBytesLenField, 
etc.).  Because of this I believe that attempting to support the main version 
of Scapy in addition to the Scapy Community repository would introduce an 
unnecessary potential for instability.

At this time EAPeak will continue to require that Scapy be installed from the 
community repository.  If you'd like to look at merging the Scapy layers and 
fields yourself I'd be happy to review a patch.

I may revisit this issue in the future if the main version of Scapy adds the 
missing layers and fields.

Original comment by zeroStei...@gmail.com on 24 Sep 2013 at 3:52

• Changed state: WontFix