8f0b88c8c8
Adds option to specify a private key .pem file when configuring TLS or SSL in AMI, HTTP, and SIP. Before this, the certificate file was used for both the public and private key. It is possible for this file to hold both, but most configurations allow for a separate private key file to be specified. Clarified in .conf files how these options are to be used. The current conf files do not explain how the private key is handled at all, so without knowledge of Asterisk's TLS implementation, it would be hard to know for sure what was going on or how to set it up. Review: http://reviewboard.digium.com/r/234/ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@190545 65c4cc65-6c06-0410-ace0-fbb531ad65f3
76 lines
2.7 KiB
Text
76 lines
2.7 KiB
Text
;
|
|
; Asterisk Builtin mini-HTTP server
|
|
;
|
|
;
|
|
; Note about Asterisk documentation:
|
|
; If Asterisk was installed from a tarball, then the HTML documentation should
|
|
; be installed in the static-http/docs directory which is
|
|
; (/var/lib/asterisk/static-http/docs) on linux by default. If the Asterisk
|
|
; HTTP server is enabled in this file by setting the "enabled", "bindaddr",
|
|
; and "bindport" options, then you should be able to view the documentation
|
|
; remotely by browsing to:
|
|
; http://<server_ip>:<bindport>/static/docs/index.html
|
|
;
|
|
[general]
|
|
;
|
|
; Whether HTTP/HTTPS interface is enabled or not. Default is no.
|
|
; This also affects manager/rawman/mxml access (see manager.conf)
|
|
;
|
|
;enabled=yes
|
|
;
|
|
; Address to bind to, both for HTTP and HTTPS. Default is 0.0.0.0
|
|
;
|
|
bindaddr=127.0.0.1
|
|
;
|
|
; Port to bind to for HTTP sessions (default is 8088)
|
|
;
|
|
;bindport=8088
|
|
;
|
|
; Prefix allows you to specify a prefix for all requests
|
|
; to the server. The default is blank. If uncommented
|
|
; all requests must begin with /asterisk
|
|
;
|
|
;prefix=asterisk
|
|
;
|
|
; Whether Asterisk should serve static content from http-static
|
|
; Default is no.
|
|
;
|
|
;enablestatic=yes
|
|
;
|
|
; Redirect one URI to another. This is how you would set a
|
|
; default page.
|
|
; Syntax: redirect=<from here> <to there>
|
|
; For example, if you are using the Asterisk-gui,
|
|
; it is convenient to enable the following redirect:
|
|
;
|
|
;redirect = / /static/config/cfgbasic.html
|
|
;
|
|
; HTTPS support. In addition to enabled=yes, you need to
|
|
; explicitly enable ssl, define the port to use,
|
|
; and have a certificate somewhere.
|
|
; sslenable=yes ; enable ssl - default no.
|
|
; sslbindport=4433 ; port to use - default is 8089
|
|
; sslbindaddr=0.0.0.0 ; address to bind to - default is bindaddr.
|
|
;
|
|
;
|
|
; sslcert=</path/to/certificate.pem> ; path to the certificate file (*.pem) only.
|
|
; sslprivatekey=</path/to/private.pem> ; path to private key file (*.pem) only.
|
|
; If no path is given for sslcert or sslprivatekey, default is to look in current
|
|
; directory. If no sslprivatekey is given, default is to search sslcert for private key.
|
|
;
|
|
; To produce a certificate you can e.g. use openssl. This places both the cert and
|
|
; private in same .pem file.
|
|
; openssl req -new -x509 -days 365 -nodes -out /tmp/foo.pem -keyout /tmp/foo.pem
|
|
;
|
|
; The post_mappings section maps URLs to real paths on the filesystem. If a
|
|
; POST is done from within an authenticated manager session to one of the
|
|
; configured POST mappings, then any files in the POST will be placed in the
|
|
; configured directory.
|
|
;
|
|
;[post_mappings]
|
|
;
|
|
; In this example, if the prefix option is set to "asterisk", then using the
|
|
; POST URL: /asterisk/uploads will put files in /var/lib/asterisk/uploads/.
|
|
;uploads = /var/lib/asterisk/uploads/
|
|
;
|