Re: Problems with open_basedir

Patrik Jansson wrote: >> Anyway, are symlinks to blame here? > I've added the real path into open_basedir, I also removed the // error > but still I get the restriction message: > So then I changed the absolute path in Joomla from /home/... to > /usr/home/... > and now I don't get the error anymore so it seems like it has something > to do > with the symbolic link after all. > > Is this considered a bug? We're running PHP 5.1.6. > If it could work using the symbolic link /home too I would really > appreciate. Well, I was never sure that it was a bug or not. I wasn't sure if it was my distro's packaging and any custom patches it applies and also where it was some x86_64 wierdness. Recently (last week) it was confirmed to me that it was not x86_64 at fault, but it was still my distro. It now looks like you're snarled by the same bug. Assuming you're not using Mandriva 2007, then I think this should be classified as a bug or regression. It could be that a security bug relating to symlinks was fixed (symlink attacks are a common vector for security issues to present themselves), and this had the inadvertant effect of causing this problem. I remeber some time ago that I looked for other people with the same issue on google etc. but came up blank. It's probably worth submitting a bug to PHP now so that the devs can comment on it. For me it's not too important as my setup was just local development on my machine (and I used symlinks to make it look like the production filesystem layout). I was albe to easly adapt my local system to work without symlinks. However, I also use a complex symlink setup on our production servers for a number of Joomla installs. (I use symlinks such that I only have one copy of the joomla source to make updating it much easier :)). We have not yet deployed PHP 5.1.6 there and I suspect I'll get bitten again by this problem. If you have the time to post a bug I'd appreciate it, if not please let me know and I'll do it. All the best. Col.