Bug#858754: dislocker: Unable to mount dislocker volume in fstab

mappu mappu04 at gmail.com
Sun Mar 26 02:23:16 UTC 2017

Package: dislocker
Version: 0.6.1-7
Severity: normal

Hi Maintainer,

I am trying to automatically load a Bitlocker drive via fstab.

My configuration is something like this:
   /dev/sdb2 /media/dislocker/ fuse.dislocker 
recovery-password=xyz-xyz-xyz-xyz-xyz-xyz,nofail 0 0

When running `mount -a`, i immediately get the error message:
   [CRITICAL] No BitLocker volume path given. Abort.

Basically, it's the same as this upstream bug[1] which is fixed in a new 

Is it possible to please package the newer release of dislocker?


1. https://github.com/Aorimn/dislocker/issues/68

-- System Information:
Debian Release: 9.0
   APT prefers testing
   APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ.utf8, LC_CTYPE=en_NZ.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dislocker depends on:
ii  libc6            2.24-9
ii  libdislocker0.6  0.6.1-7
ii  libfuse2         2.9.7-1
ii  libmbedcrypto0   2.4.2-1
ii  libruby2.3       2.3.3-1
ii  ruby             1:2.3.3

dislocker recommends no packages.

dislocker suggests no packages.

-- no debconf information

More information about the forensics-devel mailing list