On 2009-09-30 15:34 PDT, Jouni Malinen wrote:
> On Sep 30, 10:05 pm, Nelson B Bolyard wrote:
>> These issues need to be brought up to the IETF TLS mailing list, ASAP.
>> The last thing we want, IMO, is to have to implement a bunch of
>> slightly-different incompatible extractor functions. :-/
>
>
On Sep 30, 10:05 pm, Nelson B Bolyard wrote:
> These issues need to be brought up to the IETF TLS mailing list, ASAP.
> The last thing we want, IMO, is to have to implement a bunch of
> slightly-different incompatible extractor functions. :-/
It seems to be somewhat late to go through the IETF WG
On 2009-09-30 10:30 PDT, Jouni Malinen wrote:
> On Sep 29, 11:50 pm, Douglas Stebila wrote:
>> You can find a patch implementing draft-ietf-tls-extractor-07 in NSS
>> attached to bug 507359.
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=507359
>
> Thanks! This looks very useful. However, w
On Sep 29, 11:50 pm, Douglas Stebila wrote:
> You can find a patch implementing draft-ietf-tls-extractor-07 in NSS
> attached to bug 507359.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=507359
Thanks! This looks very useful. However, when testing the
implementation, I did run into interoper
You can find a patch implementing draft-ietf-tls-extractor-07 in NSS
attached to bug 507359.
https://bugzilla.mozilla.org/show_bug.cgi?id=507359
Douglas
On 2009-Sep-30, at 3:36 AM, Jouni Malinen wrote:
I'm looking into using NSS with an EAP-TLS/PEAP/TTLS/FAST
implementation. The initial par
I'm looking into using NSS with an EAP-TLS/PEAP/TTLS/FAST
implementation. The initial part of this was relatively simple to
complete since I already had a working EAP implementation with a
wrapper layer to allow the TLS/crypto library to be changed. The NSPR
file descriptor concept allowed the TLS
6 matches
Mail list logo
