[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RE: [Phpgroupware-users] open_basedir restriction

From: Dave Hall
Subject: Re: RE: [Phpgroupware-users] open_basedir restriction
Date: Wed, 01 Oct 2003 09:24:28 +1000

I have followed this thread.  Some simple tips:
* Google is your friend
* is your friend
* Read an follow "How To Ask Questions The Smart Way" -

I have just spent less than 5 mins using the above tips.  Here are the

* gave me some info on run time config
settings for php.  

* I read that page, the part i found most interesting was 
"Not every PHP directive is documented below. For a list of all
directives, please read your well commented php.ini file. You may want
to view the latest php.ini here from CVS.", so I clicked on that link.

* Searched the page for open_basedir and found, 
"; open_basedir, if set, limits all file operations to the defined directory
; and below.  This directive makes most sense if used in a per-directory
; or per-virtualhost web server configuration file. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off."

* I wanted a little more information, so went back to search the
site.  I used "open_basedir" in the "online documentation [en]" for my
search.  There was 32 google search results.  

* I selected the first option which took me to

* Again I searched the page for "open_basedir".  I found this,
"open_basedir  string

    Limit the files that can be opened by PHP to the specified
directory-tree, including the file itself. This directive is NOT
affected by whether Safe Mode is turned On or Off.

    When a script tries to open a file with, for example, fopen() or
gzopen(), the location of the file is checked. When the file is outside
the specified directory-tree, PHP will refuse to open it. All symbolic
links are resolved, so it's not possible to avoid this restriction with
a symlink.

    The special value . indicates that the directory in which the script
is stored will be used as base-directory.

    Under Windows, separate the directories with a semicolon. On all
other systems, separate the directories with a colon. As an Apache
module, open_basedir paths from parent directories are now automatically

    The restriction specified with open_basedir is actually a prefix,
not a directory name. This means that "open_basedir = /dir/incl" also
allows access to "/dir/include" and "/dir/incls" if they exist. When you
want to restrict access to only the specified directory, end with a
slash. For example: "open_basedir = /dir/incl/"

        Note: Support for multiple directories was added in 3.0.7. 

    The default is to allow all files to be opened. "

Now I don't have to be sarcastic when people are giving up their time to
 try to help me, because I can look for the answers myself.  I also know
that I may take more than 5mins to find the answers I am looking for,
but I keep on practising so I get better and faster.  I also bookmark
useful information and categorise it so it is easier to find the answers
next time.

I hope this little tutorial will help you too.



Brian Connolly <address@hidden> wrote:

> Chris,
> Yes, I am familiar with phpinfo.  Certainly lots of stuff there.  
> But with
> regards to specifics, for the most part I am able to discern blue 
> shadedwith gray.  Which color should I stress with the provider?  I 
> am rather fond
> of gray.  But if I tell the provider that, I may unduly influence 
> him.  What
> do you think?
> This has been very helpful.  I greatly appreciate your facility 
> with the
> subject.
> Brian
> -----Original Message-----
> From: address@hidden
> [mailto:phpgroupware-users-
> address@hidden On
> Behalf Of Chris Weiss
> Sent: Tuesday, September 30, 2003 2:00 PM
> To: address@hidden
> Subject: RE: [Phpgroupware-users] open_basedir restriction
> Soory, I just found it really unsettling that the title of the 
> thread is
> "open_basedir restriction", we've been talking about the open_basedir
> restriction,
> and you stop and ask "what restriction".  You can probably find the 
> info you
> need in
> a phpinfo() page, there's a link for one at the bottom of the phpgw
> administration
> section, it's in the side bar if you use iDots template.
> Brian Connolly (address@hidden) wrote:
> >
> >Chris,
> >
> >No need for insult.  What is simple to you may not be so simple to 
> others.>This is the users list.
> >
> >With regard to asking the provider, I need to be exact and 
> specific or my
> >response will be equally ambiguous.  I do not know exactly what to 
> ask.  As
> >a user, I don't know what an open_basedir restriction is.  I don't 
> knowwhat
> >your code is doing to incite it.  I assumed you would.
> >
> >Brian
> >
> >-----Original Message-----
> >From: address@hidden
> >[mailto:phpgroupware-users-
> address@hidden On
> >Behalf Of Chris Weiss
> >Sent: Tuesday, September 30, 2003 12:09 PM
> >To: address@hidden
> >Subject: RE: [Phpgroupware-users] open_basedir restriction
> >
> >Brian Connolly (address@hidden) wrote:
> >>With regard to restrictions, can you tell me what to ask the 
> provider>>please?
> >
> >oh i dunno, maybe the one we've been talking about and the Subject 
> of the
> >thread?
> >
> >
> >
> >_______________________________________________
> >Phpgroupware-users mailing list
> >address@hidden
> >
> >
> >
> >
> >
> >
> >_______________________________________________
> >Phpgroupware-users mailing list
> >address@hidden
> >
> >
> _______________________________________________
> Phpgroupware-users mailing list
> address@hidden
> _______________________________________________
> Phpgroupware-users mailing list
> address@hidden

Attachment: dave.hall.vcf
Description: Card for <>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]