Date: Wed, 9 Sep 2009 14:59:21 +0200 From: Mel Flynn <mel.flynn+fbsd.ports@mailing.thruhere.net> To: freebsd-ports@freebsd.org Cc: Alex Dupre <ale@freebsd.org> Subject: Re: security/engine_pkcs11 unable to use it Message-ID: <200909091459.22207.mel.flynn%2Bfbsd.ports@mailing.thruhere.net> In-Reply-To: <4AA78052.30909@FreeBSD.org> References: <200909082313.59252.mel.flynn%2Bfbsd.ports@mailing.thruhere.net> <200909091210.35307.mel.flynn%2Bfbsd.ports@mailing.thruhere.net> <4AA78052.30909@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 09 September 2009 12:15:46 Alex Dupre wrote:
> Mel Flynn ha scritto:
> > +post-install:
> > + @${ECHO_MSG} "You will need a criptoki library to use the
> > engine." + @${ECHO_MSG} "One is provided by security/opensc"
> > +
>
> If you need engine_pkcs11, you know what you want, the cryptoki library
> should be the start.
I was actually looking for a way to decrypt my firefox's signons3.txt, which
from searches on the net lead me to pkcs11 functions. ls security|grep pkcs11
lead me to the engine and nothing lead me to security/opensc. Granted, I
should probably have researched the standard further.
However, the configuration file issue remains. With the correct module_path
added to openssl.cnf, openssl refuses to look in /usr/local/lib/engines or to
give any indication it understands the sections added. Is this broken with the
base openssl?
--
Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909091459.22207.mel.flynn%2Bfbsd.ports>