nik/easyrsa
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Re-arrange "# Signing a request" to fix markdown problem

Browse Source 
Supercedes: #430
Closes: #47

Signed-off-by: Richard T Bonhomme <tincantech@protonmail.com>
This commit is contained in:
Richard T Bonhomme 2022-03-21 19:28:59 +00:00
parent df63c6385b
commit b02f4231a5
No known key found for this signature in database
GPG Key ID: 2D767DB92FB6C246
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/EasyRSA-Readme.md
View File

@ -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 <type> 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.