Will Veracrypt be affected in anyway by the 2038 's bug...?
I think the current "exe" version of Veracrypt 1.23 ... is a 32 bits version ?
(I own an old 32 bits CPU laptop but I have not set the clock of the BIOS to 2038 yet)
Would be curious to see .....or is Veracrypt totally proof and immune to this far away threat ?
(ZIP files and FAT files could be affected or unreadable or stay unencrypted when trying to mount them ?)
thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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......)
Hi
Will Veracrypt be affected in anyway by the 2038 's bug...?
I think the current "exe" version of Veracrypt 1.23 ... is a 32 bits version ?
(I own an old 32 bits CPU laptop but I have not set the clock of the BIOS to 2038 yet)
Would be curious to see .....or is Veracrypt totally proof and immune to this far away threat ?
(ZIP files and FAT files could be affected or unreadable or stay unencrypted when trying to mount them ?)
thanks
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...?????