| Summary: | ASTERISK-19204: Manager API opens on random port on reload, TLS address not loaded as set | ||
| Reporter: | Chris Mylonas (chris.mylonas) | Labels: | |
| Date Opened: | 2012-01-16 15:42:55.000-0600 | Date Closed: | 2012-02-02 11:05:01.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | CEL/cel_manager |
| Versions: | 1.8.8.1 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS 5, asterisk 1.8.8.1 built from source. | Attachments: | |
| Description: | Updating my manager.conf settings as per the ASTERISK-19201 issue, using tlsbindaddr in the format xxx.xxx.xxx.xxx:yyyy In manager.conf [general] enabled = yes webenabled=no port = 5038 bindaddr = 127.0.0.1 tlsenable=yes tlsbindaddr=127.0.0.1:5777 tlscert=/var/lib/asterisk/keys/astcert.pem displayconnects=yes ;only effects 1.6+ Opens the manager api on 127.0.0.1:5038 as expected. TLS manager opens on 127.0.0.1:5039 default port ignoring setting. Editing manager.conf to enabled=no and doing a "manager reload" from the CLI - the tlsbindaddr is now read in correctly but the manager api is opened on a random port number. I believe this to be a security issue perhaps? Manager API is opened, and bound to 0.0.0.0:53090 TLS Manager is opened on 127.0.0.1:5777 as expected. | ||
| Comments: | |||