[asterisk-bugs] [JIRA] (ASTERISK-28797) [patch] tcptls: Fix notice when TLS is enabled but not configured.

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250089#comment-250089 ] 

Asterisk Team commented on ASTERISK-28797:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> [patch] tcptls: Fix notice when TLS is enabled but not configured.
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-28797
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28797
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 13.32.0, 16.9.0, 17.3.0
>            Reporter: Alexander Traud
>            Severity: Trivial
>
> ASTERISK-27394 introduced a log message when Asterisk was configured (and build) without the OpenSSL Development Headers. That message is printed when a TLS _server_ is attempted by the administrator, for example through {{tlsenable=yes}} in the configuration file {{sip.conf}}.
> However
> 1. the log message did not end with a carriage return, resulting the next log message to be printed in the same line, and
> 2. another log message existed when the administrator attempted a TLS _client_.
> The attached patch adds the missing carriage return. Furthermore it uses the same wording and severity (not notice but error) for both log messages. This not only improves consistency, when both cases happen (TLS server and client requested by administrator) but also allows the administrator to distinguish which message belongs to the server and which to the client case.



--
This message was sent by Atlassian JIRA
(v6.2#6252)