Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | 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(treewide): move former git-crypted files to correct location | Silas Schöffel | 2024-04-24 |
| | | | | They were accidentally added at the wrong location in dd4b6bcfc16c7c795b697195eb6703966352d9f4 | ||
* | fix(system/services/taskserver): Add required kernel settings | Soispha | 2024-04-02 |
| | | | | | | These are the defaults, but I think it is better to explicitly state them to ensure that we don't suffer from a mistake, when we think about changing them in the future. | ||
* | chore(git-crypt): Remove `git-crypt` and associated encrypted files | Soispha | 2024-03-29 |
| | |||
* | refactor(system/services/taskserver): Move away from git-crypt | Soispha | 2024-03-29 |
| | |||
* | docs(system/services/taskserver): Add docs about expectations to runtime | Soispha | 2023-11-18 |
| | |||
* | fix(system/services/taskserver): Support both ipv4 and ipv6 | Soispha | 2023-11-18 |
| | |||
* | 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): Add a way to connect users together | Soispha | 2023-10-17 |
| | |||
* | fix(system/services/taskserver): Disable debug | Soispha | 2023-10-17 |
| | |||
* | fix(system/services/taskserver): Activate debug | Soispha | 2023-10-16 |
| | |||
* | fix(system/services/taskserver): Use correct key name (`key.pem`) | Soispha | 2023-10-16 |
| | |||
* | fix(system/services/taskserver): Switch to strings instead of paths | Soispha | 2023-10-16 |
| | |||
* | 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 | ||
* | fix(system/services/taskserver): declare certs/keys in pki.manual | sils | 2023-10-16 |
| | |||
* | feat(system/services/taskserver): change ca to letsencrypt | sils | 2023-10-16 |
| | |||
* | fix(system/services/taskserver): Hide organisations | Soispha | 2023-10-16 |
| | |||
* | fix(system/services/taskserver): Use strict certificate validation | Soispha | 2023-10-02 |
| | |||
* | fix(system/services/taskserver): Specify domain to listen on | Soispha | 2023-10-01 |
| | |||
* | feat(system/services/taskserver): Init | Soispha | 2023-10-01 |
This is the server part used in combination with Taskwarrior to regain control over the unwieldy amount of task, that accumulate over the day. |