asterisk

Commit Graph

Author	SHA1	Message	Date
Michiel van Baak	4b7b9488d7	Merged revisions 205532 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ........ r205532 \| mvanbaak \| 2009-07-09 10:31:24 +0200 (Thu, 09 Jul 2009) \| 5 lines pthread_self returns a pthread_t which is not an unsigned int on all pthread implementations. Casting it to an unsigned int fixes compiler warnings. Tested on OpenBSD and Linux both 32 and 64 bit ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.2@205535 65c4cc65-6c06-0410-ace0-fbb531ad65f3	17 years ago
Russell Bryant	2d4a63ae59	Merged revisions 205151 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ........ r205151 \| russell \| 2009-07-08 10:56:28 -0500 (Wed, 08 Jul 2009) \| 2 lines Use tabs instead of spaces for indentation. ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.2@205154 65c4cc65-6c06-0410-ace0-fbb531ad65f3	17 years ago
Russell Bryant	e97c471b2c	Merged revisions 205120 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ........ r205120 \| russell \| 2009-07-08 10:17:19 -0500 (Wed, 08 Jul 2009) \| 16 lines Move OpenSSL initialization to a single place, make library usage thread-safe. While doing some reading about OpenSSL, I noticed a couple of things that needed to be improved with our usage of OpenSSL. 1) We had initialization of the library done in multiple modules. This has now been moved to a core function that gets executed during Asterisk startup. We already link OpenSSL into the core for TCP/TLS functionality, so this was the most logical place to do it. 2) OpenSSL is not thread-safe by default. However, making it thread safe is very easy. We just have to provide a couple of callbacks. One callback returns a thread ID. The other handles locking. For more information, start with the "Is OpenSSL thread-safe?" question on the FAQ page of openssl.org. ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.2@205148 65c4cc65-6c06-0410-ace0-fbb531ad65f3	17 years ago

Author

SHA1

Message

Date

Michiel van Baak

4b7b9488d7

Merged revisions 205532 via svnmerge from

https://origsvn.digium.com/svn/asterisk/trunk

........
  r205532 | mvanbaak | 2009-07-09 10:31:24 +0200 (Thu, 09 Jul 2009) | 5 lines
  
  pthread_self returns a pthread_t which is not an unsigned int on all
  pthread implementations. Casting it to an unsigned int fixes compiler warnings.
  
  Tested on OpenBSD and Linux both 32 and 64 bit
........


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.2@205535 65c4cc65-6c06-0410-ace0-fbb531ad65f3

Russell Bryant

2d4a63ae59

Merged revisions 205151 via svnmerge from

https://origsvn.digium.com/svn/asterisk/trunk

........
  r205151 | russell | 2009-07-08 10:56:28 -0500 (Wed, 08 Jul 2009) | 2 lines
  
  Use tabs instead of spaces for indentation.
........


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.2@205154 65c4cc65-6c06-0410-ace0-fbb531ad65f3

Russell Bryant

e97c471b2c

Merged revisions 205120 via svnmerge from

https://origsvn.digium.com/svn/asterisk/trunk

........
  r205120 | russell | 2009-07-08 10:17:19 -0500 (Wed, 08 Jul 2009) | 16 lines
  
  Move OpenSSL initialization to a single place, make library usage thread-safe.
  
  While doing some reading about OpenSSL, I noticed a couple of things that
  needed to be improved with our usage of OpenSSL.
  
  1) We had initialization of the library done in multiple modules.  This has now
     been moved to a core function that gets executed during Asterisk startup.
     We already link OpenSSL into the core for TCP/TLS functionality, so this
     was the most logical place to do it.
  
  2) OpenSSL is not thread-safe by default.  However, making it thread safe is
     very easy.  We just have to provide a couple of callbacks.  One callback
     returns a thread ID.  The other handles locking.  For more information,
     start with the "Is OpenSSL thread-safe?" question on the FAQ page of
     openssl.org.
........


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.2@205148 65c4cc65-6c06-0410-ace0-fbb531ad65f3

3 Commits (bb5655de7cc0b0ab076e7b47d32013c7260de0ed)