[asterisk-bugs] [Asterisk 0011123]: [patch] Implement asterisk CLI permissions.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11123 
====================================================================== 
Reported By:                eliel
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11123
Category:                   Core-General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 87627 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-30-2007 13:50 CDT
Last Modified:              11-28-2007 14:21 CST
====================================================================== 
Summary:                    [patch] Implement asterisk CLI permissions.
Description: 
Restrict users to run only a subset of commands allow (configured by an
administrator).
You need write access to the asterisk.ctl socket file.
This is useful when you need to allow run commands on the asterisk CLI to
some users for support purposes also is a secure manner to prevent commands
like 'restart now' or 'stop now' being executed by mistake. 
====================================================================== 

---------------------------------------------------------------------- 
 eliel - 11-28-07 14:21  
---------------------------------------------------------------------- 
IgorG: and about your question if this patch could be used while running
cli commands from manager the answer is yes, if the manager username is a
real local unix user (if not, then there will be no permissions applied so
default_perm will be used). But, right now i didn't want to do such
integration, it is only needed to change NO_PERMS to the userid logged in
on the manager interface. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-28-07 14:21  eliel          Note Added: 0074509                          
======================================================================