Your message dated Fri, 07 Feb 2014 15:35:10 -0500
with message-id <[email protected]>
and subject line TCG OPAL compliant SED (encrypted) hard drives not mountable
has caused the Debian Bug report #692925,
regarding TCG OPAL compliant SED (encrypted) hard drives not mountable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
692925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692925
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mount
Version: 2.17.2-9
Severity: wishlist
The most common type of self-encrypted hard disk (aka "OPAL" SED)
cannot be mounted on Debian because the device is not properly
detected. The mount command does not prompt the user for a password.
Consequently, the drive does not unlock and cannot be mounted.
There are commercial third-party applications that can mount an OPAL
SED (as well as do key management), but none of them have been ported
to Debian. There is SecureDoc for RedHat (ref
https://wikis.utexas.edu/download/attachments/20152881/SDLinux_v5.1ReleaseNotes.txt?version=1&modificationDate=1297713493000),
and there is "Wave System" and "Bounceback" for Windows.
Although key management would be a tall request, Debian mount should
at least be able to submit a password and mount an OPAL drive. This
is essential for very basic use of the drive. ATM, only users with a
OPAL-aware BIOS can mount SEDs, and only if the drive is installed
*internally*. Debian users cannot mount an SED externally.
FYI, the 12th question on the following page gives a summary of how
these drives are mounted:
http://www.trustedcomputinggroup.org/resources/commonly_asked_questions_and_answers_on_selfencrypting_drives
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mount depends on:
ii libblkid1 2.17.2-9 block device id library
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
ii libselinux1 2.0.96-1 SELinux runtime shared libraries
ii libsepol1 2.0.41-1 SELinux library for manipulating b
ii libuuid1 2.17.2-9 Universally Unique ID library
mount recommends no packages.
Versions of packages mount suggests:
ii nfs-common 1:1.2.2-4squeeze2 NFS support files common to client
-- no debconf information
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This really isn't mount's job. The system bios should unlock the
drive, and if it doesn't, you can use hdparm to do so.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS9UN+AAoJEI5FoCIzSKrwXcgIAJi8O7ITy1yxnPiynFfUnQfH
Nqv9CX71Y5Eulf6G0PcFTs26fQbnSmi0wBp8HgPfowi9P+KItsCLcMvZkSDT/fbs
nRwhbEY6HRHLl5O1+kOw5biVFe/4E7TauIm0SRU1wFrqNV7x+voj/YYAVDEQ/yEM
wID1zhrlgdvvwXMYGaQf/U/I7xzxPiI8zEzrLbOoMiXZ1sapsYTJB5isdSGbwMWP
poh+tP91BUd5h46exb+NnDwomBQFeRMnICVEnG11vtujUgS/9Vq+K3E1c1rEt3Fv
QqNwRqABQjvS2ApGwa+jceg7msxgLZPF16ciIgL3CCMB/f+w/pf6N0t9edGlJ8U=
=dUWd
-----END PGP SIGNATURE-----
--- End Message ---
