Hi,
> On 30 Mar 2016, at 14:55, Hartmaier Alexander
> wrote:
>
> we use PEAP-TLS, EAP-PEAP as outer EAP type with EAP-TLS as inner.
> Not sure if the outher EAP-PEAP adds any real security as the Radiator
> cert is the same one for both types as it only hides the transmission of
> the user cert
Hi Tuure,
we use PEAP-TLS, EAP-PEAP as outer EAP type with EAP-TLS as inner.
Not sure if the outher EAP-PEAP adds any real security as the Radiator
cert is the same one for both types as it only hides the transmission of
the user cert which can be classified like a public key imho.
I've already tu
Hi,
> On 30 Mar 2016, at 14:13, Hartmaier Alexander
> wrote:
>
> yes this is the total auth time. Is one second a usual value for a
> PEAP-TLS auth?
>
just out of curiosity, how do you calculate the total auth time?
An EAP authentication takes around 4-10 round-trips depending on
an EAP met
Hi guys,
yes this is the total auth time. Is one second a usual value for a
PEAP-TLS auth?
There is no backend lookup involved, only cert validation against
multiple CAs their local downloaded crl files.
Best regards, Alex
On 2016-03-30 12:05, Hugh Irvine wrote:
> Hello Alex -
>
> It depends on
Hello Alex -
It depends on what you are looking at.
EAP involves multiple RADIUS messages to and from the end user device and
Radiator.
If you are looking at the overall response time from the initial RADIUS
Access-Request, through all of the EAP back and forth, to the ultimate
Access-Accept
Hi,
> On 29 Mar 2016, at 11:53, Hartmaier Alexander
> wrote:
>
> I've copied the calculation code to my LogFormatHook code:
>
> $message->{response_time} = Radius::Util::timeInterval( \
> $p->{RecvTime}, \
> $p->{RecvTimeMicros}, Radius::Util::getTimeHires()); \
>
> I'
