Home
https://www.veracrypt.fr/en/Digital%20Signatures.html mentions that there is a new fingerprint post-1.22 Why is this? How can we verify that the website has not been hacked? I won't touch the new version until this issue is resolved.
I just downloaded Veracrypt from https://www.veracrypt.fr/en/Downloads.html I calculated the fingerprint of the .tar.bz2 file and of the sha512sum file. The calculated fingerprint is 5069A233D55A0EEB174A5FC3821ACD02680D16DE. After calculating the fingerprint, I always google (or DuckDuckGo) it. There are only two results from Google. Results: https://www.veracrypt.fr/en/Downloads.html https://www.softantenna.com/softwares/6936-veracrypt Usually, there are a lot more. One of the sites that I verify...
https://www.veracrypt.fr/en/Digital%20Signatures.html mentions that there is a new fingerprint post-1.22 Why is this? How can we verify that the website has not been hacked?
I just downloaded Veracrypt from https://www.veracrypt.fr/en/Downloads.html I calculated the fingerprint of the .tar.bz2 file and of the sha512sum file. The calculated fingerprint is 5069A233D55A0EEB174A5FC3821ACD02680D16DE. After calculating the fingerprint, I always google it. There are only two results from Google. Results: https://www.veracrypt.fr/en/Downloads.html https://www.softantenna.com/softwares/6936-veracrypt Usually, there are a lot more. One of the sites that I verify from: https://security.stackexchange.com/questions/181014/how-to-verify-certificate-fingerprint...
When I mount a certain ntfs partition in Linux, Veracrypt returns: "Input/output error: /dev/sda2 The drive is damaged (there is a physical defect on it) or a cable is damaged, or the memory is malfunctioning. Please note that this is a problem with your hardware, not with VeraCrypt. Therefore, please do NOT report this as a bug/problem in VeraCrypt and please do NOT ask for help with this in the VeraCrypt Forums. Please contact your computer vendor's technical support team for assistance. Thank...
I am using Veracrypt in Linux. When I right click a mounted partition in Veracrypt, Veracrypt returns the error: "No such file or directory: xterm VeraCrypt::Process::Execute:108" What gives? Any solution?
Veracrypt would benefit from Read-Only encrypted containers for the purposes of backing up to the cloud. Currently, if you backup a container to the cloud and unknowingly (from malware or overzealous programs that open certain files, changing the 'date modified' or other attributes) or accidentally change the contents of the container, an adversary could figure out the key by looking at the changed bits and then decrypt your whole container. This was a known vulnerability with Truecrypt. So why not...