uv_ssl_t

Chainable SSL implementation for libuv

Subscribe to updates I use uv_ssl_t


Statistics on uv_ssl_t

Number of watchers on Github 38
Number of open issues 3
Average time to close an issue 2 months
Main language C
Open pull requests 1+
Closed pull requests 1+
Last commit over 2 years ago
Repo Created over 2 years ago
Repo Last Updated 9 months ago
Size 81 KB
Organization / Authorindutny
Contributors1
Page Updated
Do you use uv_ssl_t? Leave a review!
View open issues (3)
View uv_ssl_t activity
View on github
Latest Open Source Launches
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating uv_ssl_t for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

uv_ssl_t

Build Status GitHub version

HIGHLY UNSTABLE

Chainable SSL implementation for libuv based on uv_link_t.

Why?

Doing SSL asynchronously is hard. This project provides abstract interface that works well with the event loop model of libuv.

How?

The decoupled interface backend is provided by uv_link_t, and is used extensively in this project.

Example is available here.

LICENSE

This software is licensed under the MIT License.

Copyright Fedor Indutny, 2016.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

uv_ssl_t open issues Ask a question     (View All Issues)
  • about 2 years How to check client certificate
uv_ssl_t open pull requests (View All Pulls)
  • Increment versions and fix compilation issues on win32 platform
uv_ssl_t list of languages used
Other projects in C