Two different formats
foremost, it seems that :
- On “internal” storage (connected via SATA or actually external via eSATA), Windows installs “Bitlocker“. On a per-partition basis this creates encrypted partitions (not encrypted files on a normal partition).
- On “external” storage (connected via USB, whatever it actually is, e.g. a SATA hard drive), Windows installs “Bitlocker To Go“. In an otherwise normal volume (e.g. plain FAT32), this creates hundreds of small files (many empty) and a big file taking all space, which contains actual encrypted data, including executable files to enable data access on some Windows versions only.
Since Windows expects one format or the other depending on how the device is plugged ( say, the same SATA drive through USB or eSATA cable output unlike expectations ), switching rear and forth causes problems on Windows ( like : you ca n’t access your data because Windows expects the other format ). See for case Access BitLocker Encrypted Drive Externally – Microsoft Community and windows – Bitlocker-To-Go on fixed drive – Super User .
now, back to the multi-platform question.
Access Bitlocker partition on other platform: yes on Linux, probably yes on others
There is a GPL-licensed software that can read a Bitlocker device through Linux FUSE or just make a decode copy of the book. The FUSE mode is probably Linux-specific, but the “ decode to a copy ” mode may be more portable .
The software is named Dislocker. From its README :
This software has been designed to read BitLocker encrypted partitions under a Linux system. The driver used to only read volume encrypted under a Windows 7 arrangement but is now Windows Vista able and has the write functionality.
The driver can run into two unlike modes : with or without FUSE. This modality is decided at compilation fourth dimension within the Makefile .
With FUSE, you have to give the program a ride point. Once keys are decrypted, a file named `dislocker-file ‘ appears into this provide hop on point. This charge is a virtual NTFS partition, so you can mount it as any NTFS partition and then read from it or write to it .
Without FUSE, you have to give a file name where the BitLocker encrypted partition will be decrypted. This may take a long time, depending on the size of the code partition. But subsequently, once the partition is decrypted, the access to the NTFS partition will be faster. Another thing to think about is the size on your phonograph record this method want ( same size as the book you ‘re trying to decrypt ). Nethertheless, once the partition is decrypted, you can mount your file as any NTFS partition.
Access Bitlocker To Go volume on other platforms: not so far ?
This is the encase I was faced with, and noted that Dislocker could not deal with it. Reading beginning code, it is written to assume an code Bitlocker partition, not a volume filled with Bitlocker To Go files .
In this case, the answer seems “ no ”. Your best bet is probably to use a Windows machine to access files or create a virtual machine inside a non-Windows master of ceremonies .
Possible workaround
What I did is explain the case to the person that came with the code USB stick. encoding was overkill in this case, merely “ company policy ” had all Windows machine automatically turn any tuck USB stick into an code one. The file we needed was actually not sensitive at all thus he went back to his agency and sent it to me via electronic mail. besides, the file was a Microsoft Office file which is another matter. We last had the job done anyhow. : – )