From a73001d6113e2c2bfe42b5f614696f40a2bc6ead Mon Sep 17 00:00:00 2001 From: Magnus Feuer Date: Tue, 21 Jul 2015 19:20:17 -0700 Subject: Formatting fixes in security doc --- doc/rvi_security.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/rvi_security.md b/doc/rvi_security.md index d770ff9..095b2d4 100644 --- a/doc/rvi_security.md +++ b/doc/rvi_security.md @@ -155,7 +155,7 @@ Once executed, three files will be created: every RVI node that is to accept device keys and certificates signed by the certificate issuer. -### Configuring RVI to use a public root key +#### Configuring RVI to use a public root key Only ```rvi_create_device_key.py``` and ```rvi_create_certificate.py``` use the private root key stored in ```my_root_key_priv.pem```, generated above. The RVI node itself is never aware of that file. @@ -204,7 +204,7 @@ Once executed, three files will be created: itself toward another. The file is stored in JSON Web Token format. -### Configuring RVI to use a device key +#### Configuring RVI to use a device key The RVI needs the device private/public key root key, stored in ```my_device_key_priv.pem```, is referenced from the RVI's configuration @@ -288,7 +288,7 @@ Once executed, one mandatory and one optional file will be created: readable JSON form of the generated root key. -### Configuring RVI to use a certificate +#### Configuring RVI to use a certificate The RVI needs the certificates to prove its right to register and invoke services toward remote nodes. The generated certificate file, ```my_cert.jwd```, is placed in a directory with other -- cgit v1.2.1