Drive Badger is able to automatically detect and decrypt LUKS-encrypted partitions, but only using passwords (which is the most popular method anyway). It doesn't support keyfiles.
See keys-luks-demo repository. It contains a sample
You can configure multiple such repositories - each such repository should:
/opt/drivebadger/config/keys-luks-yourchosennamelocal directory on your Drive Badger persistent partition
luks.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:
luks.keys file can contain:
#sign (without leading spaces)
# laptop password MyFancyPassword # laptop alternative password (for another key slot) R3c0ve4y_p@sSw0rd-f0r-my-1@pt0p # desktop password MyLUKSBootPassword123
Similar to other partition types (except only Bitlocker), LUKS-encrypted partitions are detected by
udevd during system boot phase. Drive Badger relies on that, and just iterates over all detected partition UUIDs, trying to mount and exfiltrate them one by one.
crypto_LUKS partition type, Drive Badger checks all passwords from
luks.keys files against all 8 key slots, and when a matching key is found, it's saved in keys directory - so it can be easily reused.