LibreCrypt: Open-Source disk encryption for Windows

The latest version of this document can be found at the LibreCrypt project site

Fault/Bug Reporting

Although LibreCrypt should be pretty stable and have no faults, it's always possible that you may find something not quite right. In these cases, it would be very much appreciated if you could report it as shown in the contact details.

If you have recently upgraded to a newer version of LibreCrypt, please could you ensure that you have followed the upgrade procedure exactly before reporting a fault. (See Installation and Upgrading from a Previous Version section)

When reporting a fault with LibreCrypt, please include as much detail as possible, preferably including as much of the following as possible (Note: Not all of the following may apply):

1. What OS you're running under.
2. Any service packs which have been applied to your OS.
3. The LibreCrypt executable version (See the "Help | About..." dialog).
4. The main FreeOTFE driver version (See the "Help | About..." dialog).
5. Details of how the container in question was created (e.g. the summary shown on the last stage of creating a container).
6. The size of any container file/partition involved.
7. If using a container file, the filesystem used on the drive the container file is stored on (e.g. NTFS/FAT/FAT32).
8. The filesystem the container is formatted as (e.g. NTFS/FAT/FAT32).
9. A copy of the CDB dump taken from any container file involved (See "Tools | Critical Data Block | Dump to human readable file...").
10. If a keyfile is being used, a copy of the keyfile and password used.
11. A small test container (e.g. 1MB) which can replicate the problem found (Note: Please do *not* email container files, unless asked to! An FTP site is available for uploading these)

Some of the items listed above may include potentially sensitive data. In which case, feel free to omit that information - or better still, create a simple test case which replicates the problem, but doesn't include any such data.