aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Franke <christian.franke@t-online.de>2025-07-16 11:33:25 +0200
committerChristian Franke <christian.franke@t-online.de>2025-07-22 15:56:13 +0200
commit4613a9a9799792a53444576de61bd1569f346ffa (patch)
treee2324347fdf33a4e1294a582f9ac1bd0a0b6d648
parent437d2d6862b47c6cf10c989706eddf55e5f41efd (diff)
downloadnewlib-4613a9a9799792a53444576de61bd1569f346ffa.zip
newlib-4613a9a9799792a53444576de61bd1569f346ffa.tar.gz
newlib-4613a9a9799792a53444576de61bd1569f346ffa.tar.bz2
Cygwin: doc: add note about raw devices of BitLocker partitions
Signed-off-by: Christian Franke <christian.franke@t-online.de>
-rw-r--r--winsup/doc/specialnames.xml6
1 files changed, 6 insertions, 0 deletions
diff --git a/winsup/doc/specialnames.xml b/winsup/doc/specialnames.xml
index 02375e7..4b23200 100644
--- a/winsup/doc/specialnames.xml
+++ b/winsup/doc/specialnames.xml
@@ -361,6 +361,12 @@ the information between <filename>/proc/partitions</filename> and the
<command>df</command> output, you should be able to figure out which
external drive corresponds to which raw disk device name.</para>
+<para>Raw devices of partitions protected by BitLocker provide access to the
+<emphasis>decrypted</emphasis> NTFS image. If the partition is locked, read
+attempts fail with <literal>Permission denied</literal>. The corresponding
+block range from the raw device of the full disk provides access to the
+<emphasis>encrypted</emphasis> image as stored on the disk.</para>
+
<note><para>Apart from tape devices which are not block devices and are
by default accessed directly, accessing mass storage devices raw
is something you should only do if you know what you're doing and know how to