A very important choice I have to make between NTFS or EXFAT
for setting a Hidden volume on my brand new SD card device which is a 512 GB,
I need to have 98% of it, hidden....
so I need to make my choice for the right allocation table between NTFS or EXFAT,
I need crossplatform compatibility with Linux and Windows as well
(I would rather have NTFS if possible)
Can the hidden volume be bigger than 50% of the total size of the device ?
Indeed this is unclear to me since the NTFS file system always stores internal data exactly in the middle of the volume.
Does it really matter or not,
if it is bigger than 50% of the total size of the volume,
Will it work though ??
THANKS A LOT
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You need to format the outer volume FAT or exFAT to prevent its file table being created in the middle of the outer volume, thereby restricting the space for the hidden volume to half the total size of the outer volume, since it would need to be created after the outer volume's file table.
The hidden volume can then be almost the size of the outer volume, and can be formatted NTFS, since where its file table is located is irrelevant.
Last edit: Adrian Kentleton 2020-03-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have noticed something different (wheter you are on Linux or on Windows)
When choosing to create a Hidden Volume Partition/Device,
=> On Linux, the whole process of encrypting requires only ONCE to choose the file system,
(the Outer Volume is not asked...., the Hidden volume ONLY is asked to provide the file system...)
So I was wondering what the file system was by default for the Outer Volume....
When I mount the Outer Volume, and by checking with the DISKS app on Linux,
it clearly shows FAT (whatever and no matter the choice of file system for the Hidden volume, the Outer volume remains always FAT....)
So according to the above,
Should I be ok with my 98% NTFS Hidden Volume Partition, knowing the Outer Volume (the Shell) has been given the FAT table by default ??
=> On a Live Windows PE, it seems to me :
you can choose None File System and then after you can format with whatever file system you want (aside from Exfat which is not shown),
....probably at least for the Outer volume.....,
I will do more resarch for the Hidden Volume
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1/to update this topic, I have tried the Live Windows PE, it is possible to reformat both Outer and Hidden Volumes in :
NTFS / FAT or REFS but....not EXFAT...!!!
PS : I am going to try with a normal WIndows..... less secure since not a live CD....
2/the Exfat support should be built into Linux from Kernel 5.4
However, I used Parted Magic 2020.02.23 which runs Kernel 5.5,
and still, the Outer Volume will show FAT, non matter what......very strange, isn't it ?
3/the reason why I would rather use EXFAT as OUTERVOLUME is that FAT might be Outdated in a distant future
and not be working on January 2038
(yes it is far in the future but I like to do things correctly from the start......)
mint@mint:~/Desktop$ sudo apt install exfat-fuse exfat-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
exfat-fuse is already the newest version (1.2.8-1).
exfat-utils is already the newest version (1.2.8-1).
0 upgraded, 0 newly installed, 0 to remove and 247 not upgraded.
Hi
A very important choice I have to make between NTFS or EXFAT
for setting a Hidden volume on my brand new SD card device which is a 512 GB,
I need to have 98% of it, hidden....
so I need to make my choice for the right allocation table between NTFS or EXFAT,
I need crossplatform compatibility with Linux and Windows as well
(I would rather have NTFS if possible)
Can the hidden volume be bigger than 50% of the total size of the device ?
Indeed this is unclear to me since
the NTFS file system always stores internal data exactly in the middle of the volume.
Does it really matter or not,
if it is bigger than 50% of the total size of the volume,
Will it work though ??
THANKS A LOT
You need to format the outer volume FAT or exFAT to prevent its file table being created in the middle of the outer volume, thereby restricting the space for the hidden volume to half the total size of the outer volume, since it would need to be created after the outer volume's file table.
The hidden volume can then be almost the size of the outer volume, and can be formatted NTFS, since where its file table is located is irrelevant.
Last edit: Adrian Kentleton 2020-03-05
Thank you very much Adrian,
you are much more knowledgeable than me ;)
infodan36 - Do you realize if you have a hidden portion 98% of the total size it is going to look awful suspicious to LE or customs etc.
Philip Smith,
that's why there is the plausible deny ability....:)
I have noticed something different (wheter you are on Linux or on Windows)
When choosing to create a Hidden Volume Partition/Device,
=> On Linux, the whole process of encrypting requires only ONCE to choose the file system,
(the Outer Volume is not asked...., the Hidden volume ONLY is asked to provide the file system...)
So I was wondering what the file system was by default for the Outer Volume....
When I mount the Outer Volume, and by checking with the DISKS app on Linux,
it clearly shows FAT (whatever and no matter the choice of file system for the Hidden volume, the Outer volume remains always FAT....)
So according to the above,
Should I be ok with my 98% NTFS Hidden Volume Partition, knowing the Outer Volume (the Shell) has been given the FAT table by default ??
=> On a Live Windows PE, it seems to me :
you can choose None File System and then after you can format with whatever file system you want (aside from Exfat which is not shown),
....probably at least for the Outer volume.....,
I will do more resarch for the Hidden Volume
exFAT support is not built-in to Linux; you have to add it. See this website: https://itsfoss.com/mount-exfat/.
Thanks for the link
1/to update this topic, I have tried the Live Windows PE, it is possible to reformat both Outer and Hidden Volumes in :
NTFS / FAT or REFS but....not EXFAT...!!!
PS : I am going to try with a normal WIndows..... less secure since not a live CD....
2/the Exfat support should be built into Linux from Kernel 5.4
However, I used Parted Magic 2020.02.23 which runs Kernel 5.5,
and still, the Outer Volume will show FAT, non matter what......very strange, isn't it ?
3/the reason why I would rather use EXFAT as OUTERVOLUME is that FAT might be Outdated in a distant future
and not be working on January 2038
(yes it is far in the future but I like to do things correctly from the start......)
However, there might be a correction from Kernel 5.6 (...sorry it is in French)
https://www.lemondeinformatique.fr/actualites/lire-la-version-56-du-noyau-linux-corrige-le-bug-de-l-an-2038-78137.html
=>I still don't know if Veracrypt FAT partition/device are at risk or not from 2038...?????
4/I have used Linux Mint Tricia 19.3, Kernel5.0.0-32-generic
the Outer Volume will be mounted with FAT table, no matter what.....(see enclosed)
mint@mint:~/Desktop$ sudo add-apt-repository universe
mint@mint:~/Desktop$ sudo apt update
Ign:1 cdrom://Linux Mint 19.3 Tricia - Release amd64 20191213 bionic InRelease
Err:2 cdrom://Linux Mint 19.3 Tricia - Release amd64 20191213 bionic Release
Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Ign:5 http://packages.linuxmint.com tricia InRelease
Get:6 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:7 http://archive.canonical.com/ubuntu bionic InRelease [10.2 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:9 http://packages.linuxmint.com tricia Release [24.2 kB]
Get:10 http://packages.linuxmint.com tricia Release.gpg [819 B]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [871 kB]
Get:12 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages [2292 B]
Get:13 http://archive.canonical.com/ubuntu bionic/partner i386 Packages [2292 B]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [651 kB]
Get:15 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [651 kB]
Get:16 http://packages.linuxmint.com tricia/main i386 Packages [14.1 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [303 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [307 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [32.9 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/restricted i386 Packages [9568 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-updates/restricted Translation-en [8468 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [1010 kB]
Get:23 http://packages.linuxmint.com tricia/main amd64 Packages [14.8 kB]
Get:24 http://packages.linuxmint.com tricia/upstream i386 Packages [42.1 kB]
Get:25 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1054 kB]
Get:26 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages [442 kB]
Get:27 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [326 kB]
Get:28 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [211 kB]
Get:29 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [264 kB]
Get:30 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages [7476 B]
Get:31 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [10.1 kB]
Get:32 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [4636 B]
Get:33 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2468 B]
Get:34 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [4028 B]
Get:35 http://archive.ubuntu.com/ubuntu bionic-backports/universe i386 Packages [4028 B]
Get:36 http://archive.ubuntu.com/ubuntu bionic-backports/universe Translation-en [1900 B]
Get:37 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7976 B]
Get:38 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [38.5 kB]
Get:39 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [23.8 kB]
Get:40 http://security.ubuntu.com/ubuntu bionic-security/restricted i386 Packages [4280 B]
Get:41 http://security.ubuntu.com/ubuntu bionic-security/restricted Translation-en [6528 B]
Get:42 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [649 kB]
Get:43 http://packages.linuxmint.com tricia/upstream amd64 Packages [42.0 kB]
Get:44 http://packages.linuxmint.com tricia/backport amd64 Packages [79.3 kB]
Get:45 http://security.ubuntu.com/ubuntu bionic-security/universe i386 Packages [617 kB]
Get:46 http://packages.linuxmint.com tricia/backport i386 Packages [79.3 kB]
Get:47 http://security.ubuntu.com/ubuntu bionic-security/universe Translation-en [218 kB]
Get:48 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [42.1 kB]
Get:49 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [6760 B]
Get:50 http://security.ubuntu.com/ubuntu bionic-security/multiverse i386 Packages [4292 B]
Get:51 http://security.ubuntu.com/ubuntu bionic-security/multiverse Translation-en [2700 B]
Get:52 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2464 B]
Reading package lists... Done
E: The repository 'cdrom://Linux Mint 19.3 Tricia - Release amd64 20191213 bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
mint@mint:~/Desktop$ sudo apt install exfat-fuse exfat-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
exfat-fuse is already the newest version (1.2.8-1).
exfat-utils is already the newest version (1.2.8-1).
0 upgraded, 0 newly installed, 0 to remove and 247 not upgraded.