Actually, you can get full security with memcached on a single server if you use unix sockets rather than IP sockets.
Use the -s option: -s <file> unix socket path to listen on (disables network support) and use a path that has permissions set to only allow access to your user. You specify the same path to the socket file in your client configuration instead of an IP:port. This setup is completely secure, guaranteed by the unix kernel. Of course it means that you can only connect to it from clients on the same server, but it's your only option in this case. Mark. -- Mark Aufflick contact info at http://mark.aufflick.com/about/contact 2009/2/12 Clint Webb <[email protected]>: > I would NOT recommend using memcached on a public shared webserver. > Memcached has no authentication mechanisms, and anyone else using the > webserver will have access to get and set items in it. > > PHP has other inline caching mechanisms that would be better for your > situation. > > On Thu, Feb 12, 2009 at 6:28 AM, Dustin <[email protected]> wrote: >> >> >> On Feb 11, 1:07 pm, Frank He <[email protected]> wrote: >> > Question 1: >> >> > It seemed the memcached can not find the shared libraries, how i can inform >> > memcached the location for the installed libevent library? >> >> The easiest way to do that is via the LD_LIBRARY_PATH environment >> variable. >> >> Otherwise, passing in an rpath to the build would help. >> >> > Question 2: >> > I think only installing memcached in the web server is not enough, I still >> > need to install memcache php extension. If my hosting provider refuse to >> > install php extension for memcachd, are there any otherway to use it in my >> > shared web server? >> >> Don't know much about that. It's in their best interest to have it >> available for you. > > > -- > "Be excellent to each other" >
