Skip to content

Custom menu item #96

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

Open
degtyaryov opened this issue Dec 6, 2018 · 0 comments
Open

Custom menu item #96

degtyaryov opened this issue Dec 6, 2018 · 0 comments

Comments

@degtyaryov
Copy link

Hello.

Sorry for my bad english :-)

I use XDebug in production. Sometimes there is no possibility to reproduce the problem on the test server, so you need to understand what is happening inside php on the server.

If an unauthorized person gets XDebug access, this will lead to unpredictable consequences, and the attacker will be able to execute arbitrary code!

Therefore, 2 php-fpm are simultaneously launched on the server, in one of which XDebug is enabled. Access to XDebug is carried out on a secret cookie, which only the server can set, in javascript a cookie is not available. To set this cookie, there is a special panel with buttons for debugging in which you need to go through authorization actions in order for something to work. To show this panel you need another secret cookie that is already installed from javascript. It is not very convenient to install it each time by writing code in the chrome console. To do this, a separate plugin is also somehow not very.

It would be convenient if you could add custom buttons to the existing buttons, which could be given a name, a cookie name and its value. And of course, specify the sorting order of these buttons.

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

No branches or pull requests

1 participant