Martin Paljak martin at martinpaljak.net
Sun Aug 14 05:19:03 PDT 2011


On Sun, Aug 14, 2011 at 14:41, Andreas Metzler
<ametzler at downhill.at.eu.org> wrote:
> Hello,
> p11-kit 0.3 featured this addition:
> -----------------------------------------
>  Create a link for the proxy module.
>  * Install proxy module at its own path which is not prefixed by 'lib'
>  * Since the proxy module is the same as the library, and actually
>    needs to be loaded as the same library in memory (due to resource
>    tracking per process), use a symlink for proxy.
>  * Add a variable to the pkg-config file which shows the path
>    to the proxy module. ie:
>    $ pkg-config --variable=proxy_module p11-kit-1
>  https://bugzilla.redhat.com/show_bug.cgi?id=725905
> -----------------------------------------
> I am not familiar with the technical details of how p11-kit-proxy is
> used (I guess I am missing some basic knowledge to understand the
> documentation.), but I guess it is being dlopened. Is this correct?
> Should applications really access the *unversioned* module? Won't there
> be breakage if the p11-kit ABI breaks (e.g. changing the size of a struct)?

IMHO not, as PKCS#11 is a defined API with its own versioning and
related backwards-compatibility tricks.
Maybe I misunderstand something though..


More information about the p11-glue mailing list