Hello!!
"Nelson B Bolyard" <nel...@bolyard.me> schrieb im Newsbeitrag
news:mailman.693.1257791313.526.dev-tech-cry...@lists.mozilla.org...
On 2009-11-08 10:32 PDT, Marc Kaeser wrote:
Hello Robert,
where can I get in touch with the NSS people you told me about?
Here in this mailing list (or newsgroup, depending on how you read it).
Great! I'm using the "newsgroup-version", didn't know everybody get my
messages (hi everybody ^^)
But where do that InternalModule and its slots come from? I haven't been
able to find out for the moment. Maybe after some initialization or
something?
During NSS initialization, NSS reads in the configuration information for
the PKCS#11 modules and builds a list of known modules. One of the
modules
has typically been configured as the "internal" module. When it is added
to the list, NSS remembers that as the "internalModule". See
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/security/nss/lib/pk11wrap/pk11util.c&rev=1.57&mark=173-174#170
Thx a lot, but I guess that wasn't really the part I haven't been able to
find, even by using mxr. The point is that I haven't been able to find where
the "contents" come from, where an init process or whatever creates that
blank internalModule representation. When a new Module like that one is
created (once in the life of NSS, at init?) and referenced as
internalModule, I guess it has to be "filled in" the information needed,
like the contents of slot 0 and 1, the key-SECItem in the keys-objects of
those slots, the mechanism the key in there has been created for (3DES if I
remember well) and so on. But where in the code? Maybe you're already
pointing me to that information, but I can't see it in that part of the code
:-(
Marc
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
