Merge branch 'TinCanTech-master'

* Update EasyRSA-Readme.md
* Introduce unit test infrastucture

Signed-off-by: Richard T Bonhomme <tincantech@protonmail.com>
This commit is contained in:
Richard T Bonhomme 2022-03-21 21:37:11 +00:00
commit ff9e0d139e
No known key found for this signature in database
GPG Key ID: 2D767DB92FB6C246
2 changed files with 74 additions and 8 deletions

65
.github/workflows/action.yml vendored Normal file
View File

@ -0,0 +1,65 @@
# This is a basic workflow to help you get started with Actions
name: CI
# Controls when the action will run.
on:
# Triggers the workflow on push or pull request events but only for the master branch
push:
branches: [ master ]
pull_request:
branches: [ master ]
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "build"
xtest:
# The type of runner that the job will run on
runs-on: ubuntu-latest
env:
EASYRSA_REMOTE_CI: 1
TERM: xterm-256color
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
# Runs a single command using the runners shell
- name: Run a one-line script
run: sh op_test.sh -v
# Runs a set of commands using the runners shell
# - name: Run a multi-line script
# run: |
# echo Add other actions to build,
# echo test, and deploy your project.
# This workflow contains a single job called "build"
wtest:
# The type of runner that the job will run on
runs-on: windows-latest
env:
EASYRSA_REMOTE_CI: 1
TERM: xterm-256color
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
# Runs a single command using the runners shell
- name: Run a one-line script
run: cmd /c wop_test.bat
# Runs a set of commands using the runners shell
# - name: Run a multi-line script
# run: |
# echo Add other actions to build,
# echo test, and deploy your project.

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.