[
https://issues.apache.org/jira/browse/TS-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491764#comment-14491764
]
Susan Hinrichs commented on TS-3382:
------------------------------------
Ok. I was confused. We can set up the callback function to use
CRYPTO_THREADID_set_numeric to assign the pthread id. The callback seems to be
used by openssl in computing various random values.
SSLDiagnostic() was calling CRYPTO_thread_id() to fetch a thread ID value to
print in the diagnostic value. You could call CRYPTO_THREADID_get_numeric() to
get the previously registered thread ID, but we don't have a CRYPTO_THREADID
object at this point. Just calling pthread_self() directly here too seems to
be fine.
If the move the lowest supported openssl version to something 1.0.0 or better,
then we can leave this to be only version, since the CRYPTO_THREADID version of
the APIs appeared in openssl 1.0.0
> Complaints of CRYPTO_set_id_callback while compiling against openssl 1.1
> -------------------------------------------------------------------------
>
> Key: TS-3382
> URL: https://issues.apache.org/jira/browse/TS-3382
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 6.0.0
>
>
> CRYPTO_set_id_callback has been deprecated since openssl 1.0.0. Should
> update with the replacing call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
