[asterisk-bugs] [Asterisk 0010365]: [patch] Add manager command shell for accessing the system shell

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10365 
====================================================================== 
Reported By:                bkruse
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10365
Category:                   Core/ManagerInterface
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 77884 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-01-2007 16:24 CDT
Last Modified:              08-02-2007 06:58 CDT
====================================================================== 
Summary:                    [patch] Add manager command shell for accessing the
system shell
Description: 
This is just a quick patch for doing a system call from manager.

action:shell: Manager command "shell" - executes a command as if you were
at the shell environment

syntax:

action: shell
command: echo "haha" > /verifyworks


Will execute that command at the shell.

action: shell
command: echo "you'll see this in the return message"
getvar: true

________________________________________________________________

Current problems, if you do a system command, from the gui, try to
get the input back, will it freeze the connection if shell does not
return?

Example:
action: shell
command: while true; do echo "this will never exit :/" ; done
getvar: true

If getvar was not set, it should be fine. I am not sure of a way to
prevent
the user from doing this anyways. 



====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 08-02-07 06:58  
---------------------------------------------------------------------- 
If we continue down this path, I would suggest that you create another
permissions level in manager for this command alone.  As others have noted,
this is a dangerous command, and it should be restricted as best as
possible.

Far more important to be added to manager commands are the analogs to CLI
commands, so future admins can turn off the somewhat dangerous Command
functionality for all but themselves, without limiting the useful
functionality of AMI. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-02-07 06:58  Corydon76      Note Added: 0068303                          
======================================================================