Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | THREADING: OpenSSL 1.1 is thead-safe, rework some paragraphscmn/threading-update | Carlos Martín Nieto | 2016-11-04 | 1 | -22/+24 |
| | |||||
* | THREADING: update cURL thread safety link | Carlos Martín Nieto | 2016-11-02 | 1 | -1/+1 |
| | |||||
* | Documentation: fix small typos | Patrick Steinhardt | 2016-10-31 | 1 | -2/+2 |
| | |||||
* | Expand OpenSSL and libssh2 thread safety documentation | Stjepan Rajko | 2016-02-26 | 1 | -5/+11 |
| | |||||
* | curl: add CHANGELOG and THREADING entries | Carlos Martín Nieto | 2015-06-24 | 1 | -9/+17 |
| | |||||
* | Update THREADING and CHANGELOG with SecureTransport details | Carlos Martín Nieto | 2015-04-23 | 1 | -4/+14 |
| | |||||
* | Make the OpenSSL locking function warnings more severe | Carlos Martín Nieto | 2014-12-12 | 1 | -6/+15 |
| | | | | | Our git_openssl_set_locking() would ideally not exist. Make it clearer that we provide it as a last resort and you should prefer anything else. | ||||
* | Fix GCD typo | Ben Chatelain | 2014-11-14 | 1 | -3/+4 |
| | |||||
* | docs: explicitly document the threading caveatscmn/threading | Carlos Martín Nieto | 2014-11-01 | 1 | -0/+79 |
Talk about sharing objects and error messages; but the most important part is about what to do with the cryptographic libraries, which sadly have to become to responsibility of the application. |