the Bitlocker support is sometimes a bit rough and there's a security related issue.
@Security
If one unmounts/locks a Bitlocker drive the content of the directory is still listed. The windows explorer will close all windows related to the drive so that noone can take a peak at the file names, etc.. That's a much better solution, imho.
@Rough
To be asked for a password to unlock the drive would be great. Now it's just ~"this drive needs to be unlocked". I mean yeah, I know, that's why I clicked on it: http://snap.ashampoo.com/qMOkgvce
If you fear that the names of directories inside a drive protect by Bit-locker may be visible after the drive being locked, I advise you to also look under the following path for left-over directory names.
/localappdata\GPSoftware\Directory Opus\State Data
At least with Opus 12.4 and Windows 10, you should be prompted for a password to unlock BitLocker drives. I forget which exact version this was added in but it was fairly recently. (In fact, it already worked on Windows 7 for quite a long time, but Microsoft changed the way BitLocker works in Windows 10, which meant we no longer prompted, and nobody noticed until recently, then it was fixed.)
Opus will move up to the This PC folder if it is displaying a drive which gets removed. BitLocker is a bit unusual in that the drive still exists, just in an unreadable state, so it doesn't trigger that. Maybe there's an event we can listen for to make it happen; that will need some investigation.
The drive is locked and one can still see what's in it because the screen didn't refresh. It's the same for other windows/instances of Opus that are open.
If you fear that the names of directories inside a drive protect by Bit-locker may be visible after the drive being locked, I advise you to also look under the following path for left-over directory names.
/localappdata\GPSoftware\Directory Opus\State Data
Thanks a lot for the hint!
I checked recent.osd and discovered several directory and file names that are placed within the encrypted Bitlocker drive. Is this working as it should?
Yes, and I'd expect most programs to be the same. If you search the files in your user profile and the data in the registry you'll no doubt find many references to paths in the BitLocker volume as there is nothing special about a BitLocker drive, once it is unlocked, to any program.
Preventing any reference to any path on the BitLocker drive from leaking out into the unencrypted filesystem will be a very difficult task, unless you're very selective about which programs are used within the drive. If the filepaths themselves are confidential, not just the data, I would consider encrypting the system drive as well, as then the place where the configuration data is stored is also encrypted (when the machine is off, or you haven't logged in).
Windows also isn't really designed to mount and unmount BitLocker drives, which is something that annoys me as well (as I use one this way, although only the data is important, not the filenames, in my case). It can unmount them via the command line tool, but it's somewhat obscure and not the intended usage. (The tool also inexplicably requires admin access to do anything, even though most of the operations it does can be done without admin access; strange.) It seems Microsoft's design for BitLocker was to have encryption when the machine is turned off, in case of loss/theft, and not to protect the data when the machine is on but the data isn't actively in-use. I guess it largely makes sense, since if something is in the system then it can wait for the drive to be used, but I much prefer reducing the window of opportunity for such attacks, even if it only makes a small difference, and I've run into friction making Windows act that way (although it does work in the end, via some kludges, it's clearly not how it was designed to be used).
