Package: dislocker Version: 0.7.1-4+b1 Severity: important Tags: upstream Dear Maintainer,
I'm trying accessing a bitlocker encrypted drive created with Windows 10 version 1903. The drive is actually not accessible under Linux probably because of this bug upstream https://github.com/Aorimn/dislocker/issues/185. I've a doubt about the severity of the bug, I've set it to "important" and not to "grave", but since Windows 10 updates are mandatory, sooner or later the people affected will be the majority. The bug seems fixed in the latest version. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.3.9 (SMP w/12 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:it (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages dislocker depends on: ii libc6 2.29-3 ii libdislocker0.7 0.7.1-4+b1 ii libfuse2 2.9.9-2 ii libmbedcrypto3 2.16.3-1 ii ruby 1:2.5.2 dislocker recommends no packages. dislocker suggests no packages. -- no debconf information
