Bug 161233 - privoxy unable to resolve host names
privoxy unable to resolve host names
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-21 12:05 EDT by Martin Ebourne
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-29 06:00:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Ebourne 2005-06-21 12:05:51 EDT
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.
Comment 1 Daniel Walsh 2005-06-23 07:30:00 EDT
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
Comment 2 Martin Ebourne 2005-06-29 06:00:02 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.