So a friend of mine has been wrangling with suexec trying to configure it for his needs, and he has become quite furious over the fact that suexec isn't configurable.
Then he finds out that Debian actually has a version of suexec[1] that lets you use a conf file to configure suexec. My question is, why the heck isn't this in Fedora? How is it that Debian can offer both versions[1][2], but Fedora cannot?
I'm honestly surprised that Fedora doesn't offer this little piece of flexibility. I would think that this would be in Fedora and RHEL, because of how useful this would be. So what's going on here?
[1]: https://packages.debian.org/sid/apache2-suexec-custom [2]: https://packages.debian.org/sid/apache2-suexec-pristine
On Fri, Mar 14, 2014 at 05:16:27PM -0500, Conan Kudo (ニール・ゴンパ) wrote:
Then he finds out that Debian actually has a version of suexec[1] that lets you use a conf file to configure suexec. My question is, why the heck isn't this in Fedora? How is it that Debian can offer both versions[1][2], but Fedora cannot?
There is no ”cannot”. License seem fine, it's just a matter of packaging.
I'm honestly surprised that Fedora doesn't offer this little piece of flexibility. I would think that this would be in Fedora and RHEL, because of how useful this would be. So what's going on here?
Fedora is a community distribution. Apparently nobody needed this non-standard suexec before, therefore nobody packaged it. The only way to get custom-suexec into Fedora is by packaging it. Either by finding fellow packager or by doing it by yourself: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
On Fri, Mar 14, 2014 at 05:16:27PM -0500, Conan Kudo (ニール・ゴンパ) wrote:
I'm honestly surprised that Fedora doesn't offer this little piece of flexibility. I would think that this would be in Fedora and RHEL, because of how useful this would be. So what's going on here?
Actually a Debian developer created a patch to make suexec configurable but since it was not sent upstream, it is not easily available everywhere else. Not sure why, but the patch is not even visible in Debian's patch tracking system: http://patch-tracker.debian.org/package/apache2/2.4.7-1
So next step would be to ask the apache maintainer in Fedora whether the patch would be accepted in Fedora and if not, a separate package needs to be created.
Regards Till
Hello all,
Apologies on the necromancy here, but I finally did find the patches (after wrestling with the fact that I can't "see" the patch tracker website for some reason... is it still live?) that created it. The patches are hosted on Debian's git for packages[0]. There's some other stuff related to it one folder up[1]. I'm not exactly sure what exactly is needed, though...
[0]: http://anonscm.debian.org/cgit/pkg-apache/apache2.git/tree/debian/patches [1]: http://anonscm.debian.org/cgit/pkg-apache/apache2.git/tree/debian
On Sat, Mar 15, 2014 at 4:48 AM, Till Maas opensource@till.name wrote:
On Fri, Mar 14, 2014 at 05:16:27PM -0500, Conan Kudo (ニール・ゴンパ) wrote:
I'm honestly surprised that Fedora doesn't offer this little piece of flexibility. I would think that this would be in Fedora and RHEL, because of how useful this would be. So what's going on here?
Actually a Debian developer created a patch to make suexec configurable but since it was not sent upstream, it is not easily available everywhere else. Not sure why, but the patch is not even visible in Debian's patch tracking system: http://patch-tracker.debian.org/package/apache2/2.4.7-1
So next step would be to ask the apache maintainer in Fedora whether the patch would be accepted in Fedora and if not, a separate package needs to be created.
Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
devel@lists.stg.fedoraproject.org