Le’Sec is forged on the decentralized git forge radicle, but is also fetchable using just git.

Main repositories #

Le’Sec Stories #

The stories are all sorts of thoughts and designs.

Le’Sec Core #

The core interfaces and libraries to support interacting with plugins through their dispatch mechanism.

Le’Sec App #

The application library, with a set of functions to build applications, working as a higher level interface around the Core interfaces.

This also contains a couple of tools:

• lesec-tool

  A tool to perform cryptographic operations, given a suitable plugin.

• lesec-speed

  A tool with an interface very similar to lesec-tool, but that outputs speed measurements.

Le’Sec Plugin #

A routine library that has all the bread and butter functions that all plugins would eventually have to provide. There are dispatch functions and destructors for all current Le’Sec Core object and operation types.

This is made available for convenience. Of course, any plugin may be implemented in whatever manner the author wishes.

Plugin repositories #

ltc (plugin) #

A proof-of-concept plugin that uses libtomcrypt.

libtomcrypt is a small cryptographic algorithm library with a very easy interface, suitable enough for a proof-of-concept plugin that can do real work.

oqs (plugin) #

A proof-of-concept plugin that uses liboqs.

liboqs is an open source C library for quantum-safe cryptographic algorithms, including ML-KEM and ML-DSA.

I wanted to see how long time it would take me to wrap a working plugin around that library, and it turned out to be quite easy, it took me about a day to get something working.

Incidently, this became a proof-of-concept for Le’Sec as a whole, as lesec-speed with this plugin currently outperforms openssl speed with oqsprovider for ML-KEM.

vigenere (plugin) #

A proof-of-concept toy plugin.

‘cause why not? I wanted to see how difficult it would be to port provider-corner’s vigenere provider for OpenSSL to be used with Le’Sec applications.