Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43363 - [privoxy] Wrong configuration files ownership and permissions
Attached to Project:
Community Packages
Opened by Julien Leroux (lerouxju) - Wednesday, 07 January 2015, 10:14 GMT
Last edited by Lukas Fleischer (lfleischer) - Thursday, 29 January 2015, 09:48 GMT
Opened by Julien Leroux (lerouxju) - Wednesday, 07 January 2015, 10:14 GMT
Last edited by Lukas Fleischer (lfleischer) - Thursday, 29 January 2015, 09:48 GMT
|
DetailsDescription:
Privoxy configuration directory and files (/etc/privoxy) are owned by privoxy:privoxy with permissions 770 which is inconsistent with the rest of the system configuration files. Configuration files should be owned by root:root (and probably with different permissions) Additional info: * version: privoxy 3.0.22-1 Steps to reproduce: - Install privoxy - Check its configuration files ownership and permissions |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Thursday, 29 January 2015, 09:48 GMT
Reason for closing: Upstream
Thursday, 29 January 2015, 09:48 GMT
Reason for closing: Upstream

Files in /etc/privoxy/ are actually owned by root. There is a privoxy group to protect configuration files from other users. It is an upstream decision, though, so if you think this should be implemented another way, please report this upstream.