From b02f4231a5f0466ed936eceaefc815dd3fba7f0d Mon Sep 17 00:00:00 2001 From: Richard T Bonhomme Date: Mon, 21 Mar 2022 19:28:59 +0000 Subject: [PATCH] Re-arrange "# Signing a request" to fix markdown problem Supercedes: #430 Closes: #47 Signed-off-by: Richard T Bonhomme --- doc/EasyRSA-Readme.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/doc/EasyRSA-Readme.md b/doc/EasyRSA-Readme.md index 7bf236f..188bf5a 100644 --- a/doc/EasyRSA-Readme.md +++ b/doc/EasyRSA-Readme.md @@ -183,17 +183,18 @@ Using Easy-RSA as a CA #### Signing a request - Once Easy-RSA has imported a request, it can be reviewed and signed. Every - certificate needs a "type" which controls what extensions the certificate gets - Easy-RSA ships with 3 possible types: `client`, `server`, and `ca`, described - below: - - * client - A TLS client, suitable for a VPN user or web browser (web client) - * server - A TLS server, suitable for a VPN or web server - * ca - A intermediate CA, used when chaining multiple CAs together + Once Easy-RSA has imported a request, it can be reviewed and signed: ./easyrsa sign-req nameOfRequest + Every certificate needs a `type` which controls what extensions the certificate + gets. Easy-RSA ships with 3 possible types: `client`, `server`, and `ca`, described + below: + + * `client` - A TLS client, suitable for a VPN user or web browser (web client) + * `server` - A TLS server, suitable for a VPN or web server + * `ca` - A intermediate CA, used when chaining multiple CAs together + Additional types of certs may be defined by local sites as needed; see the advanced documentation for details.