Re: SELinux security alert/Squid -

2010-02-09 Thread Bob Goodwin
On 09/02/10 09:46, Daniel J Walsh wrote: > yum update setroubleshoot\* --enablerepo=updates-testing > Ok, I have done that on this computer and see what happens after the next re-boot. Will try it on another computer [box9] also displaying the "SELinux security alert" but with a different co

Re: SELinux security alert/Squid -

2010-02-09 Thread Daniel J Walsh
On 02/09/2010 04:43 AM, Bob Goodwin wrote: > On 09/02/10 02:17, Tim wrote: >> On Mon, 2010-02-08 at 13:23 -0500, Daniel J Walsh wrote: >> >>> squid_connect_any --> off >>> >> Probably not a good idea, the settings there as an aid to protect you >> against maliciousness. If you want to a

Re: SELinux security alert/Squid -

2010-02-09 Thread Daniel J Walsh
On 02/09/2010 08:01 AM, Bob Goodwin wrote: > On 09/02/10 07:36, Tim wrote: >> On Mon, 2010-02-08 at 16:59 -0500, Bob Goodwin wrote: >> >>> I just added "myaccount.wildblue.net" to the Firefox "no proxy for" >>> list and that seems to satisfy an access problem I didn't know I >>> had. >>>

Re: SELinux security alert/Squid -

2010-02-09 Thread Bob Goodwin
On 09/02/10 07:36, Tim wrote: > On Mon, 2010-02-08 at 16:59 -0500, Bob Goodwin wrote: > >> I just added "myaccount.wildblue.net" to the Firefox "no proxy for" >> list and that seems to satisfy an access problem I didn't know I >> had. >> > If that's you're only need to access an unusual p

Re: SELinux security alert/Squid -

2010-02-09 Thread Tim
On Mon, 2010-02-08 at 16:59 -0500, Bob Goodwin wrote: > I just added "myaccount.wildblue.net" to the Firefox "no proxy for" > list and that seems to satisfy an access problem I didn't know I > had. If that's you're only need to access an unusual port, then bypassing the proxy would be a good solut

Re: SELinux security alert/Squid -

2010-02-09 Thread Bob Goodwin
On 09/02/10 02:17, Tim wrote: > On Mon, 2010-02-08 at 13:23 -0500, Daniel J Walsh wrote: > >> squid_connect_any --> off >> > Probably not a good idea, the settings there as an aid to protect you > against maliciousness. If you want to add exceptions, that's a better > idea than just let

Re: SELinux security alert/Squid -

2010-02-08 Thread Tim
On Mon, 2010-02-08 at 13:23 -0500, Daniel J Walsh wrote: > squid_connect_any --> off Probably not a good idea, the settings there as an aid to protect you against maliciousness. If you want to add exceptions, that's a better idea than just letting anything through. I'd make an educated guess tha

Re: SELinux security alert/Squid -

2010-02-08 Thread Bob Goodwin
On 08/02/10 16:32, Daniel J Walsh wrote: > On 02/08/2010 03:16 PM, Bob Goodwin wrote: > >> On 08/02/10 13:23, Daniel J Walsh wrote: >> >> . >> Are you sure the boolean is turned on ? >> >> # getsebool squid_connect_any >> squid_connect_any --> off >> >> Once you have set the boolean on it sho

Re: SELinux security alert/Squid -

2010-02-08 Thread Daniel J Walsh
On 02/08/2010 03:16 PM, Bob Goodwin wrote: > On 08/02/10 13:23, Daniel J Walsh wrote: > > . > Are you sure the boolean is turned on ? > > # getsebool squid_connect_any > squid_connect_any --> off > > Once you have set the boolean on it should stay that way permanently if > you use the -P flag >

Re: SELinux security alert/Squid -

2010-02-08 Thread Bob Goodwin
On 08/02/10 13:23, Daniel J Walsh wrote: . Are you sure the boolean is turned on ? # getsebool squid_connect_any squid_connect_any --> off Once you have set the boolean on it should stay that way permanently if you use the -P flag # setsebool -P squid_connect_any 1 -

Re: SELinux security alert/Squid -

2010-02-08 Thread Daniel J Walsh
On 02/08/2010 04:20 AM, Bob Goodwin wrote: > Yesterday I began getting an "SELinux security alert" and Firefox began > to operate erratically [became useless]. > > I did "setsebool -P squid_connect_any=1" per the alert and Firefox began > to work again, however now this morning I am getting a si

SELinux security alert/Squid -

2010-02-08 Thread Bob Goodwin
Yesterday I began getting an "SELinux security alert" and Firefox began to operate erratically [became useless]. I did "setsebool -P squid_connect_any=1" per the alert and Firefox began to work again, however now this morning I am getting a similar notice although it appears to be making an exc