summaryrefslogtreecommitdiff
path: root/doc/manual/p11-kit-proxy.xml
diff options
context:
space:
mode:
authorStef Walter <stefw@redhat.com>2016-11-29 13:30:55 +0100
committerStef Walter <stefw@redhat.com>2016-11-29 13:32:23 +0100
commit561ee23f218c7a68a2ef46525502f978e56fc1bb (patch)
tree8deb8569f109a0e9dea11736f56ad5e47f42dc11 /doc/manual/p11-kit-proxy.xml
parenta96f354c3068edb6c8ac80ae6d9a6611651145d7 (diff)
downloadp11-kit-master.tar.gz
MOVED TO: https://github.com/p11-glue/p11-kitHEADmaster
This repository has moved to GitHub to allow further contributions and more flexibility who can merge changes. More details here: https://lists.freedesktop.org/archives/p11-glue/2016-November/000626.html
Diffstat (limited to 'doc/manual/p11-kit-proxy.xml')
-rw-r--r--doc/manual/p11-kit-proxy.xml29
1 files changed, 0 insertions, 29 deletions
diff --git a/doc/manual/p11-kit-proxy.xml b/doc/manual/p11-kit-proxy.xml
deleted file mode 100644
index 7cc3615..0000000
--- a/doc/manual/p11-kit-proxy.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
-]>
-<chapter xml:id="sharing">
- <title>Proxy Module</title>
-
- <para>When an application is aware of the fact that coordination
- is necessary between multiple consumers of a PKCS#11 module, and wants
- to load standard configured PKCS#11 modules, it can link to
- <literal>p11-kit</literal> and use the functions there to provide this
- functionality.</para>
-
- <para>However most current consumers of PKCS#11 are ignorant of
- this problem, and do not link to p11-kit. In order to solve this
- multiple initialization problem for all applications,
- <literal>p11-kit</literal> provides a proxy compatibility
- module.</para>
-
- <para>This proxy module acts like a normal PKCS#11 module, but
- internally loads a preconfigured set of PKCS#11 modules and
- manages their features as described earlier. Each slot in the configured modules
- is exposed as a slot of the <literal>p11-kit</literal> proxy module. The proxy
- module is then used as a normal PKCS#11 module would be. It can be loaded by
- crypto libraries like NSS and behaves as expected.</para>
-
- <para>The <literal>C_GetFunctionList</literal> exported entry point of the
- proxy module returns a new managed PKCS#11 module each time it is called. These
- managed instances are released when the proxy module is unloaded.</para>
-</chapter>