[asterisk-dev] RFC - TLS certificate negotiation

[Johansson Olle E]

27 nov 2006 kl. 21.05 skrev Luigi Rizzo:

> I am looking for feedback on the following issue.
>
> Right now there is TLS support in asterisk only for HTTPS.  But as
> we add it to different services (e.g. manager, SIP, and so on) we
> should decide whether we want to use a single certificate for all
> services on the same server, or let each service define its own
> certificate.
>
> Personally i cannot see a reason for managing multiple certificates
> - in the end the certificate only guarantees on the identity of the
> server, and given that all modules in asterisk see all the memory,
> we cannot limit the visibility of the private key to a single module
> anyways.
>
> This has an implication - the configuration of the certificate,
> which is basically the single line
>
> 	; sslcert=/tmp/foo.pem  ; path to the certificate
>
> should be moved to a more central place e.g. asterisk.conf, and its
> processing (basically the function ssl_setup() in main/http.c and
> associated variables) should also be moved to a more central place
> (e.g. netsock.c) and especially, called early in the boot process.
>

For SIP, we might have to have one certificate per domain.
We will have to support multihosting on TLS too.

We might want to look at the handling of SSL certs and RSA keys (IAX2)
as one central process. For the RSA keys we have initiatlization  
(pincode
check) at boot time (CLI or asterisk.conf) or at any time through a  
CLI command.

/O