Documentations

Using Cryptlib - Encryption Based On Solid Foundations

After a decent number of weeks of intense coding and testing, I have finally finished my first program clAES (sig) of the Cryptlib Tools collection. This work is the result of my attempt to use Cryptlib as the foundation for file encryption (coded in Python3) which does one thing and only that, safely encrypt or decrypt a file with password-based AES.

And nothing more.

The lessons I learned while coding clAES seem to me worth describing. So I hope, my experience with Cryptlib-coding in Python may pave the way for those of you who have developed an appetite for using Cryptlib in your own project as well.

Trying To Solve The Hen-And-Egg Problem

It is hard to secure code review of a new crypto project.

The Crypto PI

In January 2015 I announced the development of the Crypto PI on the Metzdowd Cryptography mailing list. This has evolved into the Crypto Bone Project during the year 2015 and was adapted into Fedora the next year.

Is HTTPS A Lost Cause?

Not least with Lets Encrypt the use of HTTPS has become commonplace. But HTTPS (at least how it is used in browsers) has its problems. A careful configuration of the Apache web server can mitigate some risks.

If you'll need more control over the HTTPS data transfer, you can use one of the latest developments in the Cryptlib Tools (cltls).

How To Set Up HTTPS On Your Own Web Server

A detailed description of the Apache web server configuration.