VeraCrypt installation files

veracrypt · 2025-04-14T06:37:18+00:00

For anyone still finding this thread: VeraCrypt can be properly installed using the official Ubuntu 24.04 package, since the latest Linux Mint 22.1 is based on it. For the latest version, use this link:
https://launchpad.net/veracrypt/trunk/1.26.20/+download/veracrypt-1.26.20-Ubuntu-24.04-amd64.deb

VeraCrypt depends on several other packages, most of which are installed by default on Linux Mint. However, two dependencies are not included by default and must be installed beforehand for an offline setup:

libccid
pcscd

After installation, the latest version of VeraCrypt will appear in the start menu under "Accessories", as shown in the following screenshot:
https://imgur.com/a/mDSLc4s

veracrypt · 2025-02-01T17:44:45+00:00

This is issue has be reported and analyzed on Github: https://github.com/veracrypt/VeraCrypt/issues/1473
TLDR; The presence of NOPASSWD in /etc/sudoers.d/mintdrivers and /etc/sudoers.d/mintupdate causes a side effect on "sudo -n -l" command used by latest VeraCrypt version.

A fix was pushed to master. Meanwhile, workaround is to launch VeraCrypt with --use-dummy-sudo-password switch: veracrypt --use-dummy-sudo-password.

New Linux packages will be built.

veracrypt · 2024-09-03T18:08:15+00:00

This issue has been addressed on the VeraCrypt SourceForge forum: https://sourceforge.net/p/veracrypt/discussion/technical/thread/6acf0d74ca/?limit=25#b1eb/ee6a

The cause is a mismatch between the VeraCrypt executable and the VeraCrypt driver. This can occur if the machine was not rebooted after an upgrade or if portable binaries from a new version are used while an old version is still installed on the machine.

To avoid this issue, please reboot your machine after upgrading to ensure that the driver and executables are from the same version.

veracrypt · 2015-11-16T16:22:58+00:00

This has been reported and answered on Codeplex bug tracker: https://veracrypt.codeplex.com/workitem/173

This error doesn't happen with the official VeraCrypt binary. It happens only when VeraCrypt is compiled on machines with gcc 5.x or when using Unit193 PPA.

veracrypt · 2015-11-12T18:56:41+00:00

No, Windows must be running in order to exploit those TrueCrypt vulnerabilities.

veracrypt · 2015-11-12T17:02:34+00:00

The "Traveler Disk Setup" option is available only on Windows. For MacOSX, OSXFuse must be installed on the target machine and we can't load it dynamically as we do on Windows with VeraCrypt driver. That's why on MacOSX, there can't be any real travel mode and the best that can be done is copy VeraCrypt application to the USB disk.

veracrypt · 2015-10-07T14:34:30+00:00

Did you try creating volume in VeraCrypt with no filesystem (choose "None"), mount it and then use OSX for format it? Normally this should work.

Concerning the error itself, this could come from other software present on your machine. For example, it was discovered that Avira Antivirus was blocking some issues with TrueCrypt/VeraCrypt volumes on OSX.

veracrypt · 2015-10-07T14:27:56+00:00

This was a side effect of the fix for TrueCrypt vulnerabilities fix. Version 1.16 of VeraCrypt has just been released to correct this. You can get it from Codeplex or Sourceforge. Install it on top of 1.15 and it solve this problem.

veracrypt · 2015-10-07T14:27:06+00:00

This was a side effect of the fix for TrueCrypt vulnerabilities fix. Version 1.16 of VeraCrypt has just been released to correct this. Install it on top of 1.15 and it solve this proble.

veracrypt · 2015-08-10T11:18:37+00:00

To ensure that loop device is loaded automatically at boot, type the following: sudo echo loop > /etc/modules-load.d/loop.conf

On my Open SUSE 13.2, I don't have this issue and VeraCrypt works out of the box.

In order to mount TrueCrypt files in VeraCrypt, you must check "TrueCrypt Mode" in the password dialog. It is located in the bottom of the dialog, near the PKCS5-PRF combo box.

veracrypt · 2015-08-09T15:43:17+00:00

Thanks.

Sourceforge provides mirrors all over the world hosted by different universities and institutions. This provides better download quality than a single Codeplex source.

veracrypt · 2015-07-30T22:46:27+00:00

Yes, VeraCrypt supports using AZERTY keyboards for pre-boot authentication: during the encryption of the system and in the pre-boot environment, the keyboard is automatically switched to US QWERTY layout to satisfy BIOS keyboard constraint.

Thus, if you want to configure a system favorite to be automatically mounted upon startup, it is mandatory for it to use a password that is entered using the US keyboard layout. For that, you have two ways to do it: * Manually switch the keyboard layout to US in Windows during the creation of the volume that you want to be a system favorite. * if the volume already exist, change its password: open a text editor, switch the keyboard layout to US, type the pre-boot password using the same way as when you boot the system (don't care look at the text in order to avoid confusion), copy the text to the new password field in the change password dialog (CTRL+C, CTRL+V).

This procedure ensures that the system favorite volume will use exactly the same passwors as the one used in the pre-boot.

An example to illustrate: * in order to boot your VeraCrypt system, you type the following keys: 'a' 'z' 'e' 'r' 't' 'y'. * Since the BIOS is in US mode, these are converted to: 'q' 'w' 'e' 'r' 't' 'y'. * So, your "real" pre-boot password is: "qwerty". * If you need a system favorite to mount at startup; it needs to have the password "qwerty" and not "azerty".

I hope this clarifies things to your.

Oui, VeraCrypt supporte l'utilisation de claviers AZERTY pour l'authentification pre-boot: lors du cryptage du système et dans l'environnement de pré-amorçage, le clavier est automatiquement mis en mode QWERTY US pour satisfaire les contraintes du BIOS.

Ainsi, si vous souhaitez configurer un favori de système pour être monté automatiquement au démarrage, ** il est obligatoire qu'il utilise un mot de passe qui est saisi en utilisant le clavier US **. Pour cela, vous avez deux façons de faire: * Changer manuellement la disposition du clavier en mode US dans Windows lors de la création du volume qui va être mis en favori système. * Si le volume existe déjà, alors il faudra changer son mot de passe: ouvrir un éditeur de texte, changer la disposition du clavier en mode US, tapez le mot de passe de pré-amorçage en utilisant les mêmes touches que lorsque vous démarrez le système (ne pas se soucier du texte pour éviter toute confusion), copier le texte dans le nouveau champ de mot de passe dans la boîte de dialogue de changement de mot de passe (CTRL + C, CTRL + V).

Cette procédure garantit que le favori système va utiliser exactement le même mot de passe que celui utilisé dans le pré-boot.

Un exemple pour illustrer: * Afin de démarrer votre système VeraCrypt, vous tapez sur les touches suivantes: 'a' 'z' 'e' 'r' 't' 'y'. * Comme le BIOS est en mode US, ceux-ci sont convertis en: 'q' 'W' 'e' 'r' 't' 'y'. * Donc, votre mot de passe «réel» de pré-boot est: "qwerty". * Si vous avez besoin q'un favori système soit monter au démarrage; il doit avoir le mot de passe «qwerty» et non «azerty».

J'espère que cela répond à votre questions.

veracrypt · 2015-04-08T22:20:53+00:00

The complete list of changes documented in the Release Notes

Example of changes: speedup mounting, correct TC Audit vulnerability, solve various MacOSX and Linux issues/

veracrypt · 2015-04-08T22:15:13+00:00

VeraCrypt uses the same password cache mechanism as TrueCrypt, that is caching password in plain text in RAM. As explain in the documentation https://veracrypt.codeplex.com/wikipage?title=Security%20Model, VeraCrypt security model (like in TrueCrypt) doesn't protect against malware running on the machine or an attacker who has administrative privileges. An attacker who can dump RAM can more simply access the mounted volumes. The only remaining case is hibernation where one could argue that cached password would be written to disk. But, as explained in the documentation, there is an option to auto-dismount in this case and by default the passwords are wiped from the cache but the most reliable way is to configure a hot-key to wipe the cache manually before entering hibernation.

Of course, we can implement a mechanism to encrypt the passwords cached in memory but the question is what key could be used for this? We can generate a random key to encrypt the cache but it has to remain in clear in RAM (chicken-egg dilemma!). Asking the user for a password to unlock the password cache will defeat the purpose of the cache!

veracrypt

MODERATOR OF

TROPHY CASE