Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ali-ince/cert-manager
An insecure certificate manager environment for testing
https://github.com/ali-ince/cert-manager
Last synced: 21 days ago
JSON representation
An insecure certificate manager environment for testing
- Host: GitHub
- URL: https://github.com/ali-ince/cert-manager
- Owner: ali-ince
- License: unlicense
- Created: 2022-06-14T05:42:15.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2022-06-14T08:45:38.000Z (over 2 years ago)
- Last Synced: 2024-10-30T09:41:58.539Z (2 months ago)
- Language: Shell
- Size: 9.77 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# A Simple Insecure Certificate Manager
A very simple setup to generate certificates for your local environment.
## Pre-requisites
You can use this utility either locally or with docker. With docker you don't need any other dependencies other than docker and docker-compose.
### Docker
- Docker and Docker compose
### Local
- Task (https://taskfile.dev/installation/)
- OpenSSL 1.1.1 or newer - use your platform's package manager, windows -> [Chocolatey package](https://community.chocolatey.org/packages/openssl)
- GNU CoreUtils (For Windows) [Chocolatey package](https://community.chocolatey.org/packages/gnuwin32-coreutils.portable)
## Configuration
Open ca.env and modify it to suit your needs.
## Directory Layout
### root
Contains Root CA configuration and related resources. `certs/ca.cert.pem` file contains the Root CA's certificate,
which can be used to trust any issued certiticates through this script.
### intermediate
Contains Intermediate CA configuration and related resources. `certs/intermediate.cert.pem` file contains the Intermediate CA's certificate,
and `certs/ca-chain.pem` both Root and Intermediate CA certificates.
## Tasks
### Generate a Server Certificate
To generate a server certificate with subject alternative name field set as DNS:my.example.com;
```shell
docker compose run --rm certificates server-cert HOSTNAME=my.example.com
```
or if you're running locally
```shell
task server-cert HOSTNAME=my.example.com
```
will generate a key pair and also certificates for `my.example.com`. The generated files are;
- `intermediate/private/my.example.com.key.pem` is the generated private key (no password set)
- `intermediate/certs/my.example.com.cert.pem` is the generated server certificate
- `intermediate/pkcs/my.example.com.pfx` is the PKCS12 file that contains both the private key and certificate (password is `changeit`)
If you want to add extra subject alternative names into the certificate, you can pass them with `EXTRA_SAN_LIST` option, as follows;
```shell
docker compose run --rm certificates server-cert HOSTNAME=my.example.com EXTRA_SAN_LIST="DNS:another.example.com, IP:192.168.0.110"
```
or
```shell
task server-cert HOSTNAME=my.example.com EXTRA_SAN_LIST="DNS:another.example.com, IP:192.168.0.110"
```