From b02f4231a5f0466ed936eceaefc815dd3fba7f0d Mon Sep 17 00:00:00 2001 From: Richard T Bonhomme Date: Mon, 21 Mar 2022 19:28:59 +0000 Subject: [PATCH 1/2] 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. From 7bc8d305135694852579d5befc07c054e2f6b7cb Mon Sep 17 00:00:00 2001 From: Richard T Bonhomme Date: Mon, 21 Mar 2022 20:46:49 +0000 Subject: [PATCH 2/2] Add action.yml - Initial unit-test framework Signed-off-by: Richard T Bonhomme --- .github/workflows/action.yml | 65 ++++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 .github/workflows/action.yml diff --git a/.github/workflows/action.yml b/.github/workflows/action.yml new file mode 100644 index 0000000..3dc81db --- /dev/null +++ b/.github/workflows/action.yml @@ -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. +