[asterisk-bugs] [Asterisk 0016673]: [patch] TLS socket file descriptor fails to open (with no error message in log)
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Feb 26 11:01:14 CST 2010
The following issue has been CLOSED
======================================================================
https://issues.asterisk.org/view.php?id=16673
======================================================================
Reported By: michaesc
Assigned To: dvossel
======================================================================
Project: Asterisk
Issue ID: 16673
Category: Core/Portability
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: closed
Target Version: 1.6.2.6
Asterisk Version: SVN
JIRA: SWP-779
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: reopened
Fixed in Version:
======================================================================
Date Submitted: 2010-01-22 10:55 CST
Last Modified: 2010-02-26 11:01 CST
======================================================================
Summary: [patch] TLS socket file descriptor fails to open
(with no error message in log)
Description:
On platforms missing funopen(3) or fopencookie(3) DO_SSL is undefined in
main/tcptls.h. Other files including tcptls.h will fail in their TLS
operations, because of this portability problem.
In the most basic case of configuring (in sip.conf) the TLS variables
properly, one expects the TLS logic to open the necessary TCP socket file
descriptors. Asterisk (see tcptls.c) doesn't do it on all supported
platforms, and doesn't even write any error or debug message to the log
announcing the problem.
======================================================================
----------------------------------------------------------------------
(0118599) dvossel (administrator) - 2010-02-26 11:01
https://issues.asterisk.org/view.php?id=16673#c118599
----------------------------------------------------------------------
You are right, we need to figure out a way to support TLS on Solaris.
There was a miscommunication on purpose of this issue. Your summary and
description indicated that you were simply requesting a clarification in
the log message, but you did clearly outline your recommended solution
under Additional Information involved more. The problem here is this issue
was prioritized by us with the understanding that the fix would only take a
few minutes. I know this sounds silly, but can you create a new issue for
this clearly stating the purpose is to support TLS on Solaris within the
summary so this can be re-prioritized correctly.
Issue History
Date Modified Username Field Change
======================================================================
2010-02-26 11:01 dvossel Note Added: 0118599
2010-02-26 11:01 dvossel Status assigned => closed
======================================================================
More information about the asterisk-bugs
mailing list