Description of problem: Privoxy is unable to resolve hostnames and therefore does not work. I am using it with a forward proxy line, but I suspect that doesn't matter here. Log entries such as this are present in /var/log/privoxy/logfile: Jun 21 16:55:43 Privoxy(-1208865872) Error: could not resolve hostname webproxy.company.com Entries such as this are present in /var/log/messages: Jun 21 16:55:43 lldnetsjgxqt0j kernel: audit(1119369343.990:821): avc: denied { read } for pid=26179 comm="privoxy" name=resolv.conf dev=dm-0 ino=16458 scontext=system_u:system_r:privoxy_t tcontext=system_u:object_r:etc_runtime_t tclass=file Version-Release number of selected component (if applicable): selinux-policy-targeted-1.23.16-6 privoxy-3.0.3-7 How reproducible: Every time. Steps to Reproduce: 1. Configure browser to use privoxy. 2. [Maybe configure privoxy with a forward line, but probably not necessary.] 3. Attempt to access web sites. Actual results: 404 not found, entries in log files. Expected results: Load page from website as normal. Additional info: I have done a full relabel, no change. Workaround is to disable privoxy support in selinux using gui security tool.
Do you have something in the init scripts that is recreating the /etc/resolv.conf? It's context if created via dhclient or NetoworkManager should be net_conf_t. Dan
Sorry for the noise, yes that's exactly it. I had a 'sed -i' in rc.local to append to the domain search path. I've now found the 'append domain-name' option in dhclient.conf which is how I should have fixed it in the first place, and all is well.