Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the possibility to have a read-only phpmemcacheadmin #3

Open
GoogleCodeExporter opened this issue Mar 27, 2015 · 3 comments
Open

Comments

@GoogleCodeExporter
Copy link

Having the ability to flush, add, set and delete directly from phpmemcacheadmin 
is a little bit dangerous. It would be nice - although it brings no security at 
all as it will always be possible to do it through telnet - to be able to mask 
these possibilities in order to avoid an undesired click on "flush all servers" 
by a user.

Original issue reported on code.google.com by [email protected] on 3 Dec 2010 at 4:45

@GoogleCodeExporter
Copy link
Author

Sorry, I wanted to classify it as Enhancement but can't find how to do it !

Original comment by [email protected] on 3 Dec 2010 at 4:46

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Hello

I can easily add a basic PHP authentication on commands and configuration pages
This will not be very secure, but better than nothing.

Original comment by [email protected] on 6 Dec 2010 at 9:10

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Here is a small patch for phpmemcacheadmin 1.2.0 that add a configuration 
option to activate or not "Admin mode".

In admin mode, write commands and configuration modification are hidden (no 
security here, for example accessing directly configuration.php works only the 
link is removed !). A user can have this features back by adding admin=1 GET 
variable (adding ?admin=1 to the URL)

Original comment by [email protected] on 6 Apr 2011 at 2:43

  • Added labels: ****
  • Removed labels: ****

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant