DietPi-Software | Nextcloud Talk: New coturn systemd unit on Buster #2440
Labels
Milestone
Comments
MichaIng
added a commit
that referenced
this issue
Apr 26, 2019
+ DietPi-Software | Nextcloud Talk: Do not apply TLS settings to coTURN, which has no security benefit and complicates key handling on Buster, where coTURN runs as limited user: #2592, #2440 + DietPi-Software | Nextcloud Talk: Fix wrong/outdated coTURN settings handling due to some changes with newer versions
This was referenced Apr 26, 2019
|
Ui, I already enabled logging settings for systemd unit some time ago, great! PR up to not enable TLS on coTURN anymore, since there is no security advantage and Nextcloud Talk does not use the required TURNS protocol anyway: PR up: #2740 |
MichaIng
added
Solution available 🥂
MichaIng
added a commit
that referenced
this issue
Apr 26, 2019
+ DietPi-Software | Nextcloud Talk: Do not apply TLS settings to coTURN, which has no security benefit and complicates key handling on Buster, where coTURN runs as limited user: #2592, #2440 + DietPi-Software | Nextcloud Talk: Fix wrong/outdated coTURN settings handling due to some changes with newer versions (Buster)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Buster, the
coturnAPT package now includes a systemd unit, superseding theinit.dservice.turnservernow. This means we need to adjust permissions to allow TLS with LetsEncrypt certificate. Goes hand in hand with https://github.com/Fourdee/DietPi/issues/2363 to implement TLS support for various software titles which do not use a dedicated webserver./etc/default/coturn, thus command arguments (currently logging related) need to be added via systemd unit drop-in config.ExecStartinstead of completely replacing it.$(sed ...) --no-stdout-log ...perhaps possible, but very hacky 🤔.The text was updated successfully, but these errors were encountered: