Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | feat(taskserver/certs/ca.certs.pem): Regenerate certificate taskd | Benedikt Peetz | 2024-10-05 |
| | |||
* | refactor(taskserver/certs): Format scripts and allow selecting which certs ↵ | Benedikt Peetz | 2024-10-05 |
| | | | | to generate | ||
* | chore(taskserver/certs/ca.key.pem.gpg): reencrypt with new keys as recipients | Silas Schöffel | 2024-10-05 |
| | |||
* | fix(system/services/taskserver/certs): Move cert generation to script | Soispha | 2023-11-07 |
| | | | | | | This fully removes the human-factor and allows it to just run `./generate` to generate all required certificates and keys (with the needed extra keys and certificates) | ||
* | feat(system/services/taskserver): Integrate Let's Encrypt certificates | Soispha | 2023-10-16 |
The current setup now runs the `taskserver.vhack.eu` domain with a Let's Encrypt certificate and additionally uses a self-signed CA certificate to validate clients. The shell scripts used to generate the CA certificate and the derived client certificate (and keys) are taken nearly unmodified from the upstream repository [1]. [1]: https://github.com/GothenburgBitFactory/taskserver/tree/9794cff61e56bdfb193c6aa4cebb57970ac68aef/pki |