LuaSec
Go to file
Ignacio Burgueño 8eb48c2d8b Enables building with LuaRocks and MS compilers
A patch is added to the rockspec to fix an issue in the
interaction between LuaRocks and Microsoft compilers.

LuaRocks build backend assumes the library being built will
allways export a symbol called "luaopen_<library name>". This is
not the case with LuaSec so it fails to link.
The patch just adds an empty implementation of that, so it will
properly link.
2016-01-31 15:35:19 -03:00
samples update protocol samples(bring "tlsv1_2" to clients and "any" to servers) 2015-11-17 20:39:05 -03:00
src Keep 'sslv23' for compability, but deprected. (it will be removed in the next version) 2015-11-19 12:33:06 -02:00
.gitignore gitignore build artifacts 2015-03-02 11:33:37 +01:00
CHANGELOG Version number -> 0.6 alpha 2015-08-21 11:21:16 -03:00
INSTALL Version number -> 0.6 alpha 2015-08-21 11:21:16 -03:00
LICENSE Version number -> 0.6 alpha 2015-08-21 11:21:16 -03:00
luasec-0.6alpha-3.rockspec Enables building with LuaRocks and MS compilers 2016-01-31 15:35:19 -03:00
luasec.sln LuaSec 20120616 (unofficial) + patches 2013-03-30 12:21:40 +00:00
luasec.suo LuaSec 20120616 (unofficial) + patches 2013-03-30 12:21:40 +00:00
luasec.vcproj LuaSec 0.4 2012-09-02 11:32:26 -03:00
luasec.vcxproj Set flags to compile with internal inet_ntop() by default. 2015-08-28 19:21:50 -03:00
luasec.vcxproj.filters LuaSec 20120616 (unofficial) + patches 2013-03-30 12:21:40 +00:00
Makefile bump MACOSX_VERSION 2015-10-15 08:19:29 -03:00
README.md MinGW progress. 2015-08-28 16:13:44 -03:00

LuaSec 0.6a

Alpha version to address Lua 5.2 and 5.3 compatibility.

LuaSec 0.5

LuaSec depends on OpenSSL, and integrates with LuaSocket to make it easy to add secure connections to any Lua applications or scripts.

This version includes:

  • A new certificate (X509) API, which supports:

    • Reading the subject (identity) and issuer of the certificate.
    • Reading various X509 extensions, including email and dnsName.
    • Converting certificates to and from the standard ASCII PEM format.
    • Generating the fingerprint/digest of a certificate (using SHA1, SHA256 or SHA512).
    • Reading the certificate's expiration, serial number, and other info.
  • The ability to get more detailed information from OpenSSL about why a certificate failed verification, for each certificate in the chain.

  • Flags to force acceptance of invalid certificates, e.g. to allow the use of self-signed certificates in a Trust On First Use model.

  • Flags to control checking CRLs for certificate revocation status.

  • Support for ECDH cipher suites.

  • An API to get the TLS 'finished' messages used for SASL channel binding (e.g. the SCRAM PLUS mechanisms).

The work in this release was undertaken by Kim Alvefur, Paul Aurich, Tobias Markmann, Bruno Silvestre and Matthew Wild.