On Sun, 15 Feb 2015 21:34:04 -0800
Brian Smith br...@briansmith.org wrote:
I believe there are only a small number of (hashAlgorithm, mgf alg,
salt length) combinations that need to be supported, namely these two:
[...]
The PSS RFC also says
that SHA-1 is mandatory, but that silliness is just
Hanno Böck ha...@hboeck.de wrote:
Brian Smith br...@briansmith.org wrote:
Having new oids with sane pre-defined parameters would vastly simplify
things. Back when I wrote that code I thought changing the standard is
harder than implementing the non-optimal spec, but I might've been
wrong.
To
Hi
I have compiled NSS in MacOsX (Mavericks --
https://developer.mozilla.org/en-US/docs/JSS_build_instructions_for_Mac_OS_X_10.6
-- Using the 64 Bits) but when executing the application (that is
389-ds-console) I get (that is with the compiled jar xpclass_dbg.jar):
Exception in thread main
Le 2/16/2015 6:15 AM, Brian Smith a écrit :
I want to make a proposal to get PSS support into TLS
1.3 and it would certainly help if I could say that all major TLS
libraries support it already.
First somebody needs to create a reasonable specification detailing
exactly which subset of the PSS
On Monday 16 February 2015 18:40:59 Hanno Böck wrote:
I don't really know what channels I'd have to go through to pursue
such a preset-OID. Can an OID be defined by an RFC? How does the
interaction between the OID registration and RFCs work? Is this
something the CFRG would do or some other
5 matches
Mail list logo
