From be403310650fdb0d9d84b9561dfb469bc3d3f43f Mon Sep 17 00:00:00 2001 From: Linus Nordberg Date: Fri, 3 Jan 2020 06:18:22 +0100 Subject: clean up the README's some --- README.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index ff73e18..36b8cf7 100644 --- a/README.md +++ b/README.md @@ -31,7 +31,7 @@ devices. ## Goals * Detect when a Cryptoki library operation fails and retry the - operation, possibly on another cryptographic device. + operation, possibly targeting another cryptographic device. * Provide failover and load balancing between cryptographic devices. @@ -54,16 +54,24 @@ devices. messing with TCP sessions, catch the failure (f.ex. by timing out) and retry the operation behind the back of the application. -- Migrating from one kind of HSM to another kind of HSM. p11p-daemon - can be configured to use more than one HSM. As long as they provide - the same functions using the same key(s), p11p-daemon can provide - fallback functionality for certain operations between different HSM's - from different vendors. +- When migrating from one kind of HSM to another kind of HSM. + p11p-daemon can be configured to use more than one HSM. As long as + they provide the same functions using the same key(s), p11p-daemon + can provide fallback functionality for certain operations between + different HSM's from different vendors. ## Inspiration - [p11-kit https://github.com/p11-glue/p11-kit/] +## Running automatic tests + +This should be enough to verify that all the necessary parts are in +place on your system, before getting p11p-daemon running. + + $ sudo apt install softhsm2 gnutls-bin libengine-pkcs11-openssl + $ make -C tests + ## Compiling, configuring and running p11p-daemon See p11p-daemon/README.md. -- cgit v1.1