On Tue, 22 May 2018 06:04:57 +0300
IL Ka wrote:
> I am definitely not an expert in this field, but here are some
> thoughts:
Exactly. There is always more than one way to skin a cat. I'm not
looking for a perfectly spelled out "solution" I must follow to the
letter.
> So, you can create "_fastcgi
Hello,
I am definitely not an expert in this field, but here are some thoughts:
connect to a fastcgi socket unless the socket's user and group are also
> www:www.
>
Should not unix domain sockets be treated as regular files in case
permissions?
If yes, then httpd should be able to access any fil
I am trying to tighten down some of the permissions for the listening
sockets for various web applications which are chrooted to /var/www. It
appears that httpd (which runs as user www and group www) refuses to
connect to a fastcgi socket unless the socket's user and group are also
www:www.
(I do
3 matches
Mail list logo