Re: open_basedir?
| From: | Niklas Keller | Date: | Sat, 11 May 2019 07:53:31 +0000 |
| Subject: | Re: open_basedir? | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-105673@lists.php.net to get a copy of this message | ||
> > That's exactly the reason why I'm for removing it. There will always
> > be ways to circumvent open_basedir and setups like this are insecure.
> > It gives a false sense of security. It's not better than nothing,
> > because most hosting providers would opt for a real solution instead
> > of leaving users entirely unprotected.
>
> What's your solution then? I'll be more than happy to have anything
> better that will work with thousands of users :)
Solutions that work at the OS level have been suggested in this
thread. It's not my job figuring out a solution that works better for
your business at scale.
> Also I don't get the argument that because it isn't perfect it would
> not be useful. It definitely is, as a security measure.
Quoting https://www.php.net/security-note.php:
> For Local exploits we mostly hear about open_basedir or safemode problems on shared virtual
> hosts. These two features are there as a convenience to system administrators and should in no way
> be thought of as a complete security framework. With all the 3rd-party libraries you can hook into
> PHP and all the creative ways you can trick these libraries into accessing files, it is impossible
> to guarantee security with these directives. The Oracle and Curl extensions both have ways to go
> through the library and read a local file, for example. Short of modifying these 3rd-party
> libraries, which would be difficult for the closed-source Oracle library, there really isn't
> much PHP can do about this.
The exact issue is that it appears to be good enough, but it really isn't.
> chroot isn't perfect either, but you might want to use it as well.
>
> Same for disable_functions, sure there will be ways to go around it,
> but it will still block 90% of attacks we might get. So, definitely not
> the most reliable thing, but it adds a layer that may help.
>
> I can pick the lock on my front door in about 10 minutes, a
> professional probably much less. And you can enter by breaking a window.
> But it is still effective as a security measure. And it would be silly
> if someone would come and tell me that the lock should be removed
> because it gives a false sense of security :)
My hope is that if we remove the feature, hosting providers will opt
for a proper door instead of one made from paper.
Regards, Niklas