Hello Martin,

Martin Bartosch wrote:
Hi Johnny,


I'm trying to switch my openssl version to 0.9.8 to
see  if this affects positively in the solution of the
problems I having with the nCipher.


personally I don't think it will help with your problem,
but it is of course worth a try.
(I hope I'll be able to perform some tests with the BP
soon. I will follow up with a report once I have done
this, but I cannot make any promises on this.)

Well, thanks no problem. I have done some tests but as everybody here know my perl knowledge is zero so I know I can't get a solution for that. I can only make test switching to another openssl version, another OpenCA version, changes in the configuration and that's it. But, don't worry if you can't get a solution.




I was checking your message, and I looked for the
library you talk about, but I didn't find it in the
openssl's lib directory, is this library supposed to
be there? or is this library located in the nCipher
software ? I don't have the nCipher software at hands
to look for it there, so I wanted to ask you. Would
you mind sending me a copy of the library or telling
me where to look for it?


My original post was based on an 0.9.8 snapshot.
I just checked out OpenSSL 0.9.8. It seems that the maintainers
have renamed the nCipher support library from
lib/engines/libncipher.so   to
lib/engines/libchil.so

So please check if you have libchil.so. If this is not the case,
the reason might be either your build process or the package maintainer
of your distribution.

The library is created during the build process of OpenSSL.
(Engine support must be enabled in the configure step.)
After installing OpenSSL, the shared libs are located
in opensslinstalldir/lib/engines/

The RPM Spec file shipped with OpenSSL 0.9.8 seems to omit the
lib/engines directoy. I had to add this directory to the spec file
to generate RPM packages that contain the engine support libraries.

Thanks, I will check the build in detail :-)


I'd rather not send you the library because this may cause problems
due to incompatible build and runtime environments between our systems.


Ok, no problem. I understand

Once I have the library located, I must put it on the
lib directory from my new OpenSSL and add the tags to
my token.xml. Do I have to do anything else? or is
that enough?


Modify the token.xml file to reference libchil.so, not libncipher.so.

Hope this helps,

Martin

Thanks a lot,
Johnny



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
OpenCA-Devel mailing list
OpenCA-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openca-devel



                
______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
OpenCA-Devel mailing list
OpenCA-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openca-devel

Reply via email to