That's are good ideas, I'll try them.
Thanks!!!2015-07-24 11:57 GMT-03:00 Amos Jeffries <squid3@xxxxxxxxxxxxx>:
On 25/07/2015 2:22 a.m., Jorgeley Junior wrote:
> Thank you so much for the help.
Cant be much help sorry. I'm just guessing here. Never actually run
Squid in a chroot myself.
> So, I use the directive 'chroot' in the squid.conf.
> I start squid this way:
> cd /etc/squid-3.5.6
> sbin/squid
> and it starts normally, but when I open the client browser and do an
> authentication it logs the errors and don't authenticate, but the squid
> doesn't stop running, just it logs the error and do not authenticate.
I've just looked up what is displaying that error and why. It is more of
the code wrongly using errno to display error text. So the message
itself may be bogus, but some error is happening when fork()'ing and
execv()'ing the helper process.
Some things I think you should try;
1) configure Squid with the full non-chroot path of the binary in the
auth_param line.
2) enter the chroot, downgrade yourself to the squid low-privilege user,
then try running the helper. Thats whats Squid is doing.
3) try the chroot directive in squid.conf with a '/' on the end
I'm out of ideas at this point. Apart from patching your squid to fix
the errno usage in ipcCreate() just to see if some other error message
appears. Sad thing about thtat is that I'm not sure what syscall is
supposed to be error-reported there, quite a few happen in sequence.
Amos
--
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
