[asterisk-bugs] [JIRA] (ASTERISK-24199) 'ALL' is specified in pjsip.conf.sample for TLS cipher but it is not valid
Richard Mudgett (JIRA)
noreply at issues.asterisk.org
Tue Sep 23 18:01:29 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-24199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222749#comment-222749 ]
Richard Mudgett commented on ASTERISK-24199:
--------------------------------------------
ALL does not give any control over the priority of the ciphers used. Also the option could be repeated to add more ciphers to the list of preferred ciphers to use.
> 'ALL' is specified in pjsip.conf.sample for TLS cipher but it is not valid
> --------------------------------------------------------------------------
>
> Key: ASTERISK-24199
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24199
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip
> Affects Versions: 12.4.0
> Reporter: Joshua Colp
> Assignee: Richard Mudgett
> Severity: Minor
>
> The pjsip.conf.sample file has an example IPv4 TLS transport with 'ALL' as the TLS cipher. This is not actually a valid cipher to be specified.
> Two options for fixing this exist:
> 1. Remove 'ALL' from the sample config
> 2. Add 'ALL' as a supported special cipher using pj_ssl_cipher_get_availables
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list