FS#55989 - [tor] Use upstream provideed systemd unit rather than maintain our own
Attached to Project:
Community Packages
Opened by BrLi (brli) - Saturday, 14 October 2017, 17:54 GMT
Last edited by freswa (frederik) - Tuesday, 06 October 2020, 16:50 GMT
Opened by BrLi (brli) - Saturday, 14 October 2017, 17:54 GMT
Last edited by freswa (frederik) - Tuesday, 06 October 2020, 16:50 GMT
|
Details
Description:
tor provides its own systemd units in src/tor-0.3.1.7/contrib/dist/tor.service.in please consider use it instead of using the one in tree Additional info: * package version(s) 0.3.1.7 * config and/or log files etc. ``` build() { (...) ./configure (...) --enable-systemd (...) package(){ (...) # Install systemd service file install -Dm0644 "contrib/dist/tor.service" "${pkgdir}/usr/lib/systemd/system/tor.service" } (...) ``` Steps to reproduce: the diff is attached |
This task depends upon
Closed by freswa (frederik)
Tuesday, 06 October 2020, 16:50 GMT
Reason for closing: Fixed
Additional comments about closing: tor-0.4.4.5-2 in [community-testing]
Tuesday, 06 October 2020, 16:50 GMT
Reason for closing: Fixed
Additional comments about closing: tor-0.4.4.5-2 in [community-testing]
At the very least, remove "User tor" from the tor.service file and put it in torrc instead... Allowing tor to start as root will let it bind to ports < 1024 before it drops privileges.
Also we've gotten a number of bugreports to fix the one we do provide, which were fixed piecemeal but all seem to have been fixed in the upstream file as well...