| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
|
|
|
| |
This isn't strictly necessary as we define the default config
|
|
|
|
| |
nixpkgs
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Although the page does not actually serve any content, many browsers
will still refuse to access it at all, if they have the 'https-only'
mode activated.
|
| | |
|
| |
| |
| |
| | |
This doesn't work as nginx doesn't have the right permissions.
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
This is done to comply with the naming scheme employed at `vhack.eu`.
|
| | |
| | |
| | |
| | |
| | | |
Otherwise, etebase might use the ipv6 ip, whilst nginx uses the ipv4
version. This prevents this issue
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
| | |
|
|/
|
|
|
|
| |
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)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
These stringcasts were mandatory.
This reverts commit cfdd2e350ff5df55beef4fa5b7bc11e9ff5e23c1.
|
| |
|
| |
|
| |
|
|
|
|
| |
mail
|
|
|
|
| |
webinterface
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|