Aleksey Sanin wrote:
Nope :(. After a lot of experimenting and lengthy discussions.... decided to
xmlsec test harness does not use pkcs12 at all. I made some changesGood. Seems ok to me except the
to use pkcs12 files. I'll send the changes later with more description.
BTW, openssl "make check" results are identical before and after these
changes.
--pkcs12[:name] <p12file>[,<cafile>[,<cafile>...]]]
IMHO, PKCS12 file should contain all the certs. But I guess I understand the
problem with changing tests suite :) What's the problem with NSS and PKCS8?
No way to load private key w/o public at all?
stop pursuing it.
ok, will see what can be done.
The changes in a nutshell:All seems ok to me (see note above about 1) )
What I'm looking for is a way to do some nss-specific stuffWhat about this: the xmlsec-nss creates keydb if needed (i.e. if there is nothing there)
as part of the test harness,
plus before and after executing tests you put
@rm -rf keydb
No need to have "if" in the Makefile :) Believe me, you don't want this :)
No problem.
BTW, because of OSCON I am late in reviewing the patch you've send.
I did about 30% on flights to and from Portland but there is still a lot to do. I'll try
to finish this stuff next week but I am waiting for licenses issues resolved
before I can check it in.
About licensing, all you need is something written from my company that
it is ok to contribute my work to xmlsec, right?. Will work on that next
week.
_______________________________________________ xmlsec mailing list [EMAIL PROTECTED] http://www.aleksey.com/mailman/listinfo/xmlsec
