Resolved What speaks against including /dev/urandom in openbasedir settings?

[Bitpalast]

How to set up php custom php settings for the domain

Why is /dev/urandom not included in openbasedir settings by default? I am trying to think of a vulnerability that this could open, but as it is a device and cannot be "deleted" or modified by PHP, why would that path not be in the openbasedir paths by default? Or am I wrong and PHP could tamper with /dev/urandom?

 

[IgorG]

I think this is done because it's impossible to add everything to the open_basedir by default, so the customization ability was added

 

[Bitpalast]

OK, I did several tests yesterday, too, with PHP scripts that tried to attack that location. Everything worked fine, no successfull attack possible, so i think it is o.k. to add it to the open_basedir path.