On 04/02/2016 12:56 PM, Stefan Fritsch wrote:
> If suexec allowed to suid to a user different than the owner of a
> script, on that server it would allow any local user to execute any
> script as any other user. Even if suexec checked that the script is
> owned by a special "trusted" user, it
On Friday 01 April 2016 14:03:12, montt...@heavyspace.ca wrote:
> On 2016-03-30 16:35, Jacob Champion wrote:
> >> Sorry, but that is not a good approach. You must assume that a
> >> local attacker calls suexec directly and passes arguments of his
> >> liking. That is the attack vector that
On 2016-03-30 16:35, Jacob Champion wrote:
Sorry, but that is not a good approach. You must assume that a local
attacker calls suexec directly and passes arguments of his liking.
That is the attack vector that suexec's rather annoying restrictions
try to avoid.
Checking my own understanding...
On 2016-03-30 14:49, Stefan Fritsch wrote:
On Saturday 19 March 2016 11:09:40, montt...@heavyspace.ca wrote:
Since its been a while since this issue was mentioned, this patch
allows Apache to suexec files by a different (but still restricted
by UID) owner, to avoid the security issue where
On 03/30/2016 01:49 PM, Stefan Fritsch wrote:
> You are doing the configuration parsing in httpd, and then pass the
> allowed uid/group to suexec as command line arguments.
>
> Sorry, but that is not a good approach. You must assume that a local
> attacker calls suexec directly and passes
On Saturday 19 March 2016 11:09:40, montt...@heavyspace.ca wrote:
> Since its been a while since this issue was mentioned, this patch
> allows Apache to suexec files by a different (but still restricted
> by UID) owner, to avoid the security issue where apache forces you
> to suexec to files it
I promise to look deeply into this post 2.4.19 release.
> On Mar 19, 2016, at 1:09 PM, montt...@heavyspace.ca wrote:
>
> Since its been a while since this issue was mentioned, this patch allows
> Apache to suexec files by a different (but still restricted by UID) owner, to
> avoid the security
On 19 March 2016, montt...@heavyspace.ca wrote:
>Since its been a while since this issue was mentioned, this patch
>allows
>Apache to suexec files by a different (but still restricted by UID)
>owner, to avoid the security issue where apache forces you to suexec to
>files it has full chmod access
Since its been a while since this issue was mentioned, this patch allows
Apache to suexec files by a different (but still restricted by UID)
owner, to avoid the security issue where apache forces you to suexec to
files it has full chmod access to.
Original Message
Subject:
