search

bobranten / Ext4Fsd

Ext4 file system driver for Windows
869 stars 56 forks source link

Veracrypt support #41

Open albertvaka opened 8 months ago

albertvaka commented 8 months ago

Veracrypt decrypts disks by creating a virtual unit with a letter from an encrypted volume path, eg: \Device\Harddisk0\Partition1 becomes F: which give access to the decrypted data. However if it's an ext4 filesystem, F: can't be read by Windows anyway.

Would it be possible for Ext4Fsd to then mount the drive by its letter instead of only allowing mounting from device paths? That is: veracrypt reads \Device\Harddisk0\Partition1 and creates F: decrypted, then Ext4Fsd reads F: and creates G: which can be used.

Does this make some sense at least?

Edit: I can see that Veracrypt also creates device paths like \Device\VeraCryptVolumeA for the decrypted partitions, so it should be possible to mount that if Ext4Fsd's Mount.exe allowed passing the full device path and not just the hard disk and partition numbers.

albertvaka commented 8 months ago

This is the line that would need changing to support arbitrary device paths: https://github.com/bobranten/Ext4Fsd/blob/d9da413ad28afa3c0519d730da60f8598bbaea32/Ext2Mgr/MountPoints.cpp#L105