Frank Higgens <[EMAIL PROTECTED]> wrote:
> Here is some more information that might help. The
> EAP-TLS packet that is received is poorly formated.
> After the normal EAP header, the EAP-TLS packet
> only contains the flags '0xC0' and then the packet
> ends. Since the 'length included' flag is set
Alan,
Here is some more information that might help. The
EAP-TLS packet that is received is poorly formated.
After the normal EAP header, the EAP-TLS packet
only contains the flags '0xC0' and then the packet
ends. Since the 'length included' flag is set in the
flags portion, the packet should co
Frank Higgens <[EMAIL PROTECTED]> wrote:
> I am running some EAP-TLS tests against our AP using
> freeradius 0.8.1 as the authentication server.
>
> I ran into a crash running a EAP DoS attack that sent
> a EAP TLS packet with flags 'c0' and with no TLS
> message length or TLS message data. The t
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
I am running some EAP-TLS tests against our AP using
freeradius 0.8.1 as the authentication server.
I ran into a crash running a EAP DoS attack that sent
a EAP TLS packet with flags 'c0' and with no TLS
message length or TLS message
