On Wed, Mar 17, 2010 at 10:20:39AM +0100, Jean-Marc Desperrier wrote: > I'm not sure. As the page says : "The current implementation does not > conform to that defined in the CMMF draft, and we intend to change this > implementation to that defined in the CMC RFC." > > Implementing it to do something non-standard and that nobody else does > would probably not get in. Now if you have the time to check the CMC > RFC, and do what's described there.
My idea was to implement the middleware between Javascript popChallengeResponse and the underlying code from CMMF. When The underlying code will become RFC compliant, the Javascript API will become RFC compliant too without a change. A working Javascript popChallengeResponse would be nice to work o n the underlying code to make it RFC complient. For now, security/nss/cmd/crmf-cgi/crmfcgi.c contains some code that cannot even be tested, since it produces an unimplemented Javascript call. -- Emmanuel Dreyfus m...@netbsd.org -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
