30.03.2009 kl. 18:30 skrev Anthony Scarpino: > John Zolnowsky x69422/408-404-5064 wrote: >>> Date: Sat, 28 Mar 2009 04:02:08 +0100 >>> From: Andreas Portele <ultrasparc at rechnerpool.de> >>> 28.03.2009 kl. 03:41 skrev John Zolnowsky x69422/408-404-5064: >>>>> Date: Sat, 28 Mar 2009 03:01:07 +0100 >>>>> From: Andreas Portele <ultrasparc at rechnerpool.de> >>>>> >>>>> I have a wired problem loading a signed kcf crypto provider. I was >>>>> already able to load it back in time, but it stopped working for >>>>> some >>>>> unknown reason. [...] >>>>> >>>>> #elfsign verify -v padlock >>> elfsign: verification of padlock passed. >>> format: rsa_sha1. >>> signer: C=US, CN=portele. >> ^^^^^^^^^^^^^^^^ >> The padlock crypto module was not signed with a cryptographic >> framework >> key/certificate pair. For example: >> # elfsign verify -v /kernel/crypto/aes >> elfsign: verification of /kernel/crypto/aes passed. >> format: rsa_sha1. >> signer: O=Sun Microsystems Inc, OU=Solaris Cryptographic Framework, >> CN=SunOS 5.10. >> signed on: Wed Dec 10 22:59:42 2008.
This was it! THX.. I had for whatever reason another cert with the same key as the cert I got from Anthony Scarpino so an elfsign verify does fine all the time, as the module loading does, as long I didn't fill in a cipher function. So this all was completely wired, but it works now with the right cert :-))
