| Summary: | ASTERISK-13171: Action: SIPpeers requires write permissions in manager interface | ||
| Reporter: | Joel N. Weber II (nemo) | Labels: | |
| Date Opened: | 2008-12-07 17:44:02.000-0600 | Date Closed: | 2011-06-07 14:07:58 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Action: IAXpeers works with read access. By contrast, Action: SIPpeers requires write access. I believe that they are both commands which only involve reading, and therefore I believe SIPpeers should be changed to work with read-only access. | ||
| Comments: | By: Tilghman Lesher (tilghman) 2008-12-08 11:42:16.000-0600 You're incorrect as to what it requires. IAXpeers requires no permission at all, while SIPpeers requires the SYSTEM privilege. Given that any change would not be backwards compatible to previous versions of 1.4 and since this lack of permissions is not a security issue, it is unlikely to be changed in 1.4 at all, but it may be changed in trunk to require equivalent permission in the IAXpeers command. By: Leif Madsen (lmadsen) 2008-12-11 12:39:02.000-0600 This is assigned to me, but what do you want me to test? By: Leif Madsen (lmadsen) 2008-12-11 14:10:53.000-0600 Aha, per Tilghman on IRC, he just wanted my suggestion as to the behaviour here. My suggestion would be that both should require the SYSTEM priviledge in order to be consistant. Thanks! By: Tilghman Lesher (tilghman) 2009-01-08 16:49:21.000-0600 Trunk already requires the SYSTEM privilege for the IAXpeers command. | ||