[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1018695: Please allow bitlocker cryptsetup devices



Package: pmount
Version: 0.9.99-alpha-1.1
Severity: wishlist

Currently, pmount has only support for LUKS and LUKS2. However, for the
sake of file exchange with windows, it would be nice to enable bitlocker
devices too.

This should be strait forward as cryptsetup already supports bitlocker.
The devices are also easy to identify.

It would be also nice to support veracrypt but it is not so easy to
identify the devices.

-- System Information:
Debian Release: bookworm/sid
  APT prefers experimental
  APT policy: (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.17 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pmount depends on:
ii  libblkid1  2.38.1-1devuan1
ii  libc6      2.34-7

pmount recommends no packages.

Versions of packages pmount suggests:
ii  cryptsetup  2:2.5.0-2
-- 
Klaus Ethgen                                       http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16            Klaus Ethgen <Klaus@Ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C

Attachment: signature.asc
Description: PGP signature


Reply to: