Drive Badger is able to automatically detect and decrypt Bitlocker-encrypted partitions, but only using recovery keys. It doesn't support other Bitlocker methods: PIN, password, FVEK files, TPM interactions etc., as these methods cannot be automated.
See keys-bitlocker-demo repository. It contains a sample
You can configure multiple such repositories - each such repository should:
/opt/drivebadger/config/keys-bitlocker-yourchosennamelocal directory on your Drive Badger persistent partition
bitlocker.keysfile with proper contents (see below)
Local directory doesn't need to contain
.git subdirectory, in fact it can be just "floating" directory (created by hand or script, without repository). However if it does, then you can update it automatically using
/opt/drivebadger/update.sh (in just 1 step for all repositories).
If you have decryption keys associated (directly or indirectly) with particular drive serial numbers, you can save such keys in keys directory.
If you have any additional useful information about particular keys, allowing you to split them in some way (eg. into cities, buildings, floors, company departments, employee specialties) into smaller groups, you can try:
bitlocker.keys file can contain:
#sign (without leading spaces)
# my laptop 1 123456-123456-123456-123456-123456-123456-123456-123456 # my laptop 2 987654-321987-987654-321987-987654-321987-987654-321987
As opposed to other encryption schemes, Bitlocker encrypted partitions are not detected by
udevd and not accessible via UUID. Therefore, they are detected in a special way, after processing all partitions that have assigned UUID: