Hi,
I want to create a skin with limited capabilities (only email management).
First of all, I created a skin from the default one without any link to unwanted sections.
But then I also want to allow only email management via commands.allow and commands.deny.
The problem is that I cannot find some documentation and examples (this http://www.directadmin.com/features.php?id=1171 is too little...)
Making some experiments, it seems that only commands.deny works fine, while I need to use commands.allow (because
I need to allow only a small subset of commands and deny the others).
For example, let's say that the user is "bob" and the domain is "domain.com".
If commands.allow is NOT present in /usr/local/directadmin/data/users/bob/ and the content of commands.deny is
CMD_SHOW_DOMAIN
CMD_API_SHOW_DOMAIN
the user bob can do anything but not execute:
http://www.domain.com:2222/CMD_SHOW_DOMAIN?domain=domain.com
(The request you've made cannot be executed because it does not exist in your authority level)
And this is correct.
If commands.deny is NOT present in /usr/local/directadmin/data/users/bob/ and the content of commands.allow is
CMD_SHOW_DOMAIN
CMD_API_SHOW_DOMAIN
the user bob can do NOTHING, even:
http://www.domain.com:2222/CMD_SHOW_DOMAIN?domain=domain.com
is not allowed! (The request you've made cannot be executed because it does not exist in your authority level)
It is not clear to me how these two files (commands.allow and commands.deny) work together.
I thought that I could use only commands.allow with the list of allowed commands...
Anyone can help me?
Thank you in advance.
I want to create a skin with limited capabilities (only email management).
First of all, I created a skin from the default one without any link to unwanted sections.
But then I also want to allow only email management via commands.allow and commands.deny.
The problem is that I cannot find some documentation and examples (this http://www.directadmin.com/features.php?id=1171 is too little...)
Making some experiments, it seems that only commands.deny works fine, while I need to use commands.allow (because
I need to allow only a small subset of commands and deny the others).
For example, let's say that the user is "bob" and the domain is "domain.com".
If commands.allow is NOT present in /usr/local/directadmin/data/users/bob/ and the content of commands.deny is
CMD_SHOW_DOMAIN
CMD_API_SHOW_DOMAIN
the user bob can do anything but not execute:
http://www.domain.com:2222/CMD_SHOW_DOMAIN?domain=domain.com
(The request you've made cannot be executed because it does not exist in your authority level)
And this is correct.
If commands.deny is NOT present in /usr/local/directadmin/data/users/bob/ and the content of commands.allow is
CMD_SHOW_DOMAIN
CMD_API_SHOW_DOMAIN
the user bob can do NOTHING, even:
http://www.domain.com:2222/CMD_SHOW_DOMAIN?domain=domain.com
is not allowed! (The request you've made cannot be executed because it does not exist in your authority level)
It is not clear to me how these two files (commands.allow and commands.deny) work together.
I thought that I could use only commands.allow with the list of allowed commands...
Anyone can help me?
Thank you in advance.
