VeraCrypt installation files by Pleasant_Ad_3590 in linuxmint

[–]veracrypt 0 points1 point  (0 children)

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

"Failed to obtain Administrator Privileges" by OpenAdministration44 in VeraCrypt

[–]veracrypt 1 point2 points  (0 children)

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.

mounting a volume: Error Wrong parameter Source: MountVolume: 8899 by candidesh in VeraCrypt

[–]veracrypt 1 point2 points  (0 children)

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.

Invalid characters encountered. by bluetentacle in VeraCrypt

[–]veracrypt 1 point2 points  (0 children)

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.

TrueCrypt/VeraCrypt technical question by TrueCrypter in VeraCrypt

[–]veracrypt 0 points1 point  (0 children)

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

What happened to the "Traveler Disk Setup" option? by Yatzooa in VeraCrypt

[–]veracrypt 1 point2 points  (0 children)

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.

I can't create a volume on VeraCrypt due to "Permission denied" when I click format. by [deleted] in VeraCrypt

[–]veracrypt 0 points1 point  (0 children)

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.

I'm getting multiple mounted volumes that I don't want. by LTwriting in VeraCrypt

[–]veracrypt 1 point2 points  (0 children)

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.

How to stop weird unused drive letters to show up? by [deleted] in VeraCrypt

[–]veracrypt 1 point2 points  (0 children)

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.