Jay Potter wrote:
> Hi, I'm new to NSS. I'm involved with a project that uses Pre-Shared
> Keys for TLS - AES-256. (RFC 4279). I get the key from an external
> module (both Client and Server). This implementation would be perfect
> for my application. I would like to see Mozilla handle this ci
Jay Potter wrote:
Any suggestions on what I would need to do to get this implimented?
A lot of convincing that it is worth doing, to begin with. IMO,
pre-shared keys have no place in a general-purpose Internet browser such
as Mozilla. The authors of RFC4279 agree - see section 1.1 .
" T
Steve Parkinson wrote:
> I like the way the .NET API is consistent, and whether you use C#,
> Managed C++, or Visual basic, the API is always the same.
>
> If we leave the OO implementation up to the scripting language wrapper,
> then we will potentially have a different API for each language.
I
Heikki Toivonen wrote:
Steve Parkinson wrote:
3) NSS is a fairly object-oriented API. But, it lacks a formal
definition of the objects, and how they interrelate. As such, it
is not possible to get swig to automate the creation of language
specific classes.
For example, many of the CERT_*
Steve Parkinson wrote:
> 1) Private function definitions. SWIG can make wrapper functions for all
I am slightly in favor of explicitly listing the functions to export in
.i files.
> 3) NSS is a fairly object-oriented API. But, it lacks a formal
> definition of the objects, and how they interrela
Rich Megginson wrote:
Steve Parkinson wrote:
I've been playing with SWIG a little. It seems too easy!
My comments so far:
1) Private function definitions. SWIG can make wrapper functions for all
functions declared in the header files. But, not all of those end up
being exposed in the .so, (d
Hi, I'm new to NSS. I'm involved with a project that uses Pre-Shared
Keys for TLS - AES-256. (RFC 4279). I get the key from an external
module (both Client and Server). This implementation would be perfect
for my application. I would like to see Mozilla handle this cipher set.
Any suggest
Steve Parkinson wrote:
I've been playing with SWIG a little. It seems too easy!
My comments so far:
1) Private function definitions. SWIG can make wrapper functions for all
functions declared in the header files. But, not all of those end up
being exposed in the .so, (due to nss.def). You re
8 matches
Mail list logo