Konstantin Andreev wrote:
> On 08/03/10 19:13, Brian Smith wrote:
> > I think I found a problem with the GCM interface that seems
> > to make it impossible to use the PKCS#11 interface in a
FIPS-140-compliant
> > manner. In particular, NIST SP800-38D requires that the IV for the GCM
mode be
> > gen
On 08/03/10 19:13, Brian Smith wrote:
Martin Paljak wrote:
At the same time, isn't GCM only present in the latest 2.30 draft?
Yes. And, actually, I think I found a problem with the GCM interface that seems
to make it impossible to use the PKCS#11 interface in a FIPS-140-compliant
manner. In
Martin Paljak wrote:
> FYI, OpenSC project [1] has a "fork" of the PKCS#11 headers [2].
Yes, I read the discussion about that and it also seems iffy. If Mozilla
already has explicit permission to distribute them under the LGPL/GPL/MPL
then that works much better.
> At the same time, isn't GCM onl
FYI, OpenSC project [1] has a "fork" of the PKCS#11 headers [2].
At the same time, isn't GCM only present in the latest 2.30 draft?
[1] https://www.opensc-project.org/opensc
[2] https://www.opensc-project.org/opensc/browser/trunk/src/pkcs11/pkcs11.h
On Aug 2, 2010, at 10:10 PM, Brian Smith wro
On Mon, Aug 2, 2010 at 12:10 PM, Brian Smith wrote:
> I read a rumor that Mozilla received explicit permission from RSA labs to
> distribute the PKCS#11 header files under the Mozilla tri-license. Does
> anybody know anything about that, and how I can verify it?
That's also what I heard. I don't
I read a rumor that Mozilla received explicit permission from RSA labs to
distribute the PKCS#11 header files under the Mozilla tri-license. Does
anybody know anything about that, and how I can verify it?
I noticed that the header files are out of date. They do not include the
AES-GCM mechanism
6 matches
Mail list logo
