Re: slowcgi -u user option does not change socket ownership

2018-08-13 Thread Florian Obser
Appologies for the delay, I have been busy with other things. It's commited now. Thanks, Florian On Fri, Aug 10, 2018 at 03:49:09PM -0500, Andrew Daugherity wrote: > I think the -U/-u options are a good solution; hopefully that will be merged? > > I noticed a small inconsistency in the logging:

Re: slowcgi -u user option does not change socket ownership

2018-08-10 Thread Andrew Daugherity
I think the -U/-u options are a good solution; hopefully that will be merged? I noticed a small inconsistency in the logging: slowcgi_user is logged at warn (which I think is too loud), whereas the chroot and socket paths are at debug, and the new sock_user setting isn't logged at all. I've

Re: slowcgi -u user option does not change socket ownership

2018-08-06 Thread Andrew Daugherity
On Fri, Aug 3, 2018 at 2:34 AM Florian Obser wrote: > > On Thu, Aug 02, 2018 at 04:22:35PM -0500, Andrew Daugherity wrote: > > I'm also playing around with a version that accepts "-U user:group" (a > > la chown), which I think would be preferable to a separate group > > Eww, do you really have a

Re: slowcgi -u user option does not change socket ownership

2018-08-03 Thread Florian Obser
On Thu, Aug 02, 2018 at 04:22:35PM -0500, Andrew Daugherity wrote: > On Wed, Aug 1, 2018 at 6:09 AM Florian Obser wrote: > > > > Nice to see it being useful on other systems, too. :) > > > > Does this work for you? > > [diff snipped] > > Yes, that works great! > Although I think you want to

Re: slowcgi -u user option does not change socket ownership

2018-08-02 Thread Andrew Daugherity
On Wed, Aug 1, 2018 at 6:09 AM Florian Obser wrote: > > Nice to see it being useful on other systems, too. :) > > Does this work for you? > [diff snipped] Yes, that works great! Although I think you want to capitalize "Change" in the man page. I'm also playing around with a version that accepts

Re: slowcgi -u user option does not change socket ownership

2018-08-01 Thread Jason McIntyre
On Wed, Aug 01, 2018 at 12:57:18PM +0200, Florian Obser wrote: > On Tue, Jul 31, 2018 at 06:39:18PM -0500, Andrew Daugherity wrote: > [...] > > Related: in the same section of code (at the end of my diff actually, > > as context), I noticed that when -u is used, the chroot path is set to > > the

Re: slowcgi -u user option does not change socket ownership

2018-08-01 Thread Florian Obser
Nice to see it being useful on other systems, too. :) Does this work for you? diff --git slowcgi.8 slowcgi.8 index 117228403b4..10bd40d2e60 100644 --- slowcgi.8 +++ slowcgi.8 @@ -25,6 +25,7 @@ .Op Fl d .Op Fl p Ar path .Op Fl s Ar socket +.Op Fl U Ar user .Op Fl u Ar user .Sh DESCRIPTION

Re: slowcgi -u user option does not change socket ownership

2018-08-01 Thread Florian Obser
On Tue, Jul 31, 2018 at 06:39:18PM -0500, Andrew Daugherity wrote: [...] > Related: in the same section of code (at the end of my diff actually, > as context), I noticed that when -u is used, the chroot path is set to > the target user's home directory instead of /var/www. I found this >

Re: slowcgi -u user option does not change socket ownership

2018-07-31 Thread Andrew Daugherity
On Sun, Jul 29, 2018 at 11:07 AM, Florian Obser wrote: > It is behaving as intended. The slowcgi.sock is for the webserver to > interact with. The specified user is not supposed to interact with the > socket. CGI scripts are executed as this user. > > slowcgi itself can use the socket just fine

Re: slowcgi -u user option does not change socket ownership

2018-07-29 Thread Florian Obser
On Thu, Jul 26, 2018 at 05:31:39PM -0500, andrew.daugher...@gmail.com wrote: > >Synopsis:slowcgi -u user option does not change socket ownership > >Category:user > >Environment: > System : OpenBSD 6.3 > Details : OpenBSD 6.3 (GENERIC.MP) #4:

slowcgi -u user option does not change socket ownership

2018-07-26 Thread andrew . daugherity
>Synopsis: slowcgi -u user option does not change socket ownership >Category: user >Environment: System : OpenBSD 6.3 Details : OpenBSD 6.3 (GENERIC.MP) #4: Sun Jun 17 11:22:20 CEST 2018 r...@syspatch-63-amd64.openbsd.org:/us