mirror of
https://github.com/brunoos/luasec.git
synced 2024-11-07 22:18:27 +01:00
LuaSec
d6b2fd7d35
Either intentionaly or due to bug in openssl in some marginal cases SSL_send reports SYSCALL error whilst errno is set to 0. This either could mean that SSL_send did not made any system call or errno were prematurely reset with consequent syscalls. And in consequence sendraw() is not propagate correct errno ends up in infinite loop trying to send same data. Such behaviour was usually observed after third consequential failed SSL send attempt which application was not aware of. First send failed with syscall errno 32 (Broken pipe) second one with SSL error 0x1409e10f (bad length) and lastly next send attemt results with SYSCALL error and errno 0. Tested using: * OpenSSL v1.1.1 * musl v1.1.20 (c50985d5c8e316c5c464f352e79eeebfed1121a9) * Linux 4.4.60+yocto armv7l |
||
---|---|---|
samples | ||
src | ||
.gitignore | ||
CHANGELOG | ||
INSTALL | ||
LICENSE | ||
luasec-1.0.1-1.rockspec | ||
luasec.sln | ||
luasec.vcxproj | ||
Makefile | ||
README.md |
LuaSec 1.0.1
LuaSec depends on OpenSSL, and integrates with LuaSocket to make it easy to add secure connections to any Lua applications or scripts.
Documentation: https://github.com/brunoos/luasec/wiki