Originally Posted by
cohaku1359
The way i understand it(and im very new to this so i could be totally wrong) is when you created an encrypted partition in VeraCrypt, you have to tell veracrypt which type of file system to use. Fat, NTFS, etc... and since i need to be able to mount that partition on a windows machine, i cant choose a native linux file system since that wouldn't mount to a windows machine, correct? or if it did mount it would not work since its not a supported file system. the r-pi NAS just shows up as a network drive(correct use of drive? it is in fact a hard drive?), on that drive is the encrypted file that veracrypt then mounts as another partition.
If the file system will be directly connected to both MS-Windows AND Linux systems, then you are correct.
If the file system will be directly connected to your NAS AND accessed over the network by any OSes, then you are incorrect. The network protocol handles any compatibility layer requirements and since a r-pi is likely running some version of Linux, then you should be using LUKS + some native Linux file system inside.
I think you are being confused by the r-pi in the mix. If that is where the storage is physically connected (don't get me started why using a r-pi for most server needs isn't the best idea), then the file systems need to be native Linux. Well, "need' is perhaps too strong a term, but it will make your life 10x easier.
And again, it isn't about hard drives. It is all about file systems, usually inside partitions. MSFT has been misleading you for decades.
Typically, this is how storage is handled.
Code:
HDD
├── part-01
│** └── Encryption-Container-01
│** └── File_System-01
├── part-02
│** └── Encryption-Container-02
│** └── File_System-02
└── part-03
└── Encryption-Container-03
└── File_System-03
That's all within 1 HDD. The fact that many people don't create separate partitions or separate encryption-containers doesn't change anything. This is just as valid:
Code:
HDD
└── part-01
└── Encryption-Container-01
└── File_System-01
In the simplest use.
Of course, Veracrypt can put a hidden encryption-container inside the same partition, if we ask it to do this. There would be another file system inside that.
Anyway, I guess the question is why did you mention the r-pi at all, if the storage isn't directly connected to it? That's what I find confusing. Time for bed here.