The ModuleLoad AMI action currently does not restrict the path given to the configured modules directory. While this AMI action is behind the system level of access, we believe it would be better if the action enforced the configured directory, similar to other functionality in Asterisk. Before we do anything though, we wanted to get some input from the community. Would this impact anyone? If so, what is your use case? Any feedback is appreciated!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.