Quantcast
Channel: VeraCrypt
Viewing all 7620 articles
Browse latest View live

New Post: opening a volume is too slow

$
0
0
I would like to keep discussions on this forum focused on VeraCrypt and not turns into fight over opinions. I'm obliged to delete the posts that are not related to VeraCrypt in order to keep a good spirit on this forum.

The user base of VeraCrypt encompasses people from different backgrounds and not necessary well versed in security, so there will be always disagreements about what is expected from VeraCrypt. But at the end, we must keep an open space for exchange of ideas with all due respect.

As for the evolution of VeraCrypt, every decision is weighted carefully and nothing is done without a deep evaluation of its security and usability impact. The discussion forums are also a way to receive feedback from the community and share ideas with other security experts.

New Post: opening a volume is too slow

$
0
0
Re-reading proj964's posts it is clear I was subject to trolling and I regrettably took the bait. No one could seriously suggest a delay in opening a volume should have any relevance on the decision for the secure number of iterations within veraCrypt. I suspect he is from a rival project or commercial software product, of course this will be denied :)

Catering to the lowest skilled and least security aware users with the poorest performing hardware is precisely what stifled Truecrypts development. I do not want to see VeraCrypt fall into the same trap.

Often I find the type mentioned above have little actual need for very strong security but by placating their demands to dumb down, will only weaken security offered to those who need it.

Please, please, please do not allow yourself to be persuaded away from the goal of the best security possible by pandering to suggestions to cripple VeraCrypt. Once you start such appeasement it is difficult to stop. Simple to use programs exist for these users already.

Clearly it is entirely up to you how you progress, your decision regarding this issue will be seen as an indication of your commitment to the policy of maximum security in VeraCrypt from now on and into the future.

I simply do not believe after all the good work already done to VeraCrypt you will start to back down now and intentionally weaken it.

I will voluntarily refrain from the forum until your intentions are made clear on this thread, to save any unpleasantness.

New Post: opening a volume is too slow

$
0
0
My intentions are clear and simple: provide the best possible security. This has driven VeraCrypt since the beginning and it will stay as it sole objective.

Concerning the exchanges on this thread, I think we should refrain from judging the intentions of those who post on the forum even if there are certainly those who have another agenda behind there postings. It is better to stick with the topic and give precise and decisive answers without being drawn into virulent exchanges.

I'm considering the deletion of this whole thread. After all, it doesn't add anything new since I already posted on this subject before.

New Post: opening a volume is too slow

$
0
0
I am happy as I believe you will remain consistent and as you say, provide the best possible security within VeraCrypt. :)

I apologise for defending VeraCrypt so vigorously, I can relax a little now I know you will not be easily influenced by these people.

Yes as you imply, this thread is simply a tautology of previous threads, it contains nothing of value. Deletion would be welcomed.

New Post: Auto Close Pop Up

$
0
0
I could not find any clean solution to disable this message and the solution propose in the link is a hack that is difficult to make it work across different languages.

His idea is to wait for a dialog to be displayed that has the title "Microsoft Windows" and which contains a button with a specific label depending on the language of the machine ( it is "Format Disk" in English, "Datenträger formatieren" in German...) and then close this Window.
The first difficulty is to dynamically load the correct value of the label depending on the language of the machine. I'm not sure we can encode in VeraCrypt all possible values of this label.

The other difficulty is that we have to implement a monitoring thread in VeraCrypt that will enumerate all top-level windows on the screen (EnumWindows)in order to find if the prompt message we are targeting is displayed. This enumerating must be done periodically with a short period time and this will consume a lot of the machine resources.

Of course, there is a less resource extensive solution by using a global system hook (SetWindowsHookEx) but this will definitely make the Antivirus bells ringing and we don't want that.

As a conclusion, while this feature is very interesting, for now there is no acceptable technical solution to implement it.

New Post: Multiple Hidden Containers

$
0
0
This idea would work but it is technically complex.
Actually, it can be generalized in order to permit the usage of an external volume header for any encrypted volume/partition. This can be seen as a format of two-factor authentication (2FA): you need the password and you need to posses the volume header which must be stored separately from the encrypted volume.

Updated Wiki: Troubleshooting

$
0
0

Troubleshooting

This section presents possible solutions to common problems that you may run into when using VeraCrypt.
Note: If your problem is not listed here, it might be listed in one of the following sections:
Make sure you use the latest stable version of VeraCrypt. If the problem is caused by a bug in an old version of VeraCrypt, it may have already been fixed. Note: SelectHelp>About to find out which version you use.

 


Problem:
Writing/reading to/from volume is very slow even though, according to the benchmark, the speed of the cipher that I'm using is higher than the speed of the hard drive.
Probable Cause:
This is probably caused by an interfering application.
Possible Solution:
First, make sure that your VeraCrypt container does not have a file extension that is reserved for executable files (for example, .exe, .sys, or .dll). If it does, Windows and antivirus software may interfere with the container and adversely affect the performance of the volume.
Second, disable or uninstall any application that might be interfering, which usually is antivirus software or automatic disk defragmentation tool, etc. In case of antivirus software, it often helps to turn off real-time (on-access) scanning in the preferences of the antivirus software. If it does not help, try temporarily disabling the virus protection software. If this does not help either, try uninstalling it completely and restarting your computer subsequently.

Problem:
VeraCrypt volume cannot be mounted; VeraCrypt reports "Incorrect password or not a VeraCrypt volume".
Possible Cause:
The volume header may have been damaged by a third-party application or malfunctioning hardware component.
Possible Solutions:
  • You can try to restore the volume header from the backup embedded in the volume by following these steps:
    1. Run VeraCrypt.
    2. Click Select Device or Select File to select your volume.
    3. Select Tools > Restore Volume Header.

Problem:
After successfully mounting a volume, Windows reports "This device does not contain a valid file system" or a similar error.
Probable Cause:
The file system on the VeraCrypt volume may be corrupted (or the volume is unformatted).
Possible Solution:
You can use filesystem repair tools supplied with your operating system to attempt to repair the filesystem on the VeraCrypt volume. In Windows, it is the 'chkdsk' tool. VeraCrypt provides an easy way to use this tool on a VeraCrypt volume: First, make a backup copy of the VeraCrypt volume (because the 'chkdsk' tool might damage the filesystem even more) and then mount it. Right-click the mounted volume in the main VeraCrypt window (in the drive list) and from the context menu select 'Repair Filesystem'.

Problem:
When trying to create a hidden volume, its maximum possible size is unexpectedly small (there is much more free space than this on the outer volume).
Probable Causes:
  1. The outer volume has been formatted as NTFS
  2. Fragmentation
  3. Too small cluster size + too many files/folders in the root directory of the outer volume.
Possible Solutions:
Solution Related to Cause 1:
Unlike the FAT filesystem, the NTFS filesystem always stores internal data exactly in the middle of the volume. Therefore, the hidden volume can reside only in the second half of the outer volume. If this constraint is unacceptable, do one of the following:
  • Reformat the outer volume as FAT and then create a hidden volume within it.
  • If the outer volume is too large to be formatted as FAT, split the volume to several 2-terabyte volumes (or 16-terabyte volumes if the device uses 4-kilobyte sectors) and format each of them as FAT.
Solution Related to Cause 2:
Create a new outer volume (defragmentation is not a solution, because it would adversely affect plausible deniability – see section Defragmenting).
Solution Related to Cause 3:
Note: The following solution applies only to hidden volumes created within FAT volumes.
Defragment the outer volume (mount it, right-click its drive letter in the 'Computer' or 'My Computer' window, clickProperties, select the Tools tab, and click 'Defragment Now'). After the volume is defragmented, exitDisk Defragmenter and try to create the hidden volume again.

If this does not help, delete all files and folders on the outer volume by pressing Shift+Delete, not by formatting, (do not forget to disable the Recycle Bin and System Restore for this drive beforehand) and try creating the hidden volume on this completely empty outer volume again (for testing purposes only). If the maximum possible size of the hidden volume does not change even now, the cause of the problem is very likely an extended root directory. If you did not use the 'Default' cluster size (the last step in the Wizard), reformat the outer volume and this time leave the cluster size at 'Default'.
If it does not help, reformat the outer volume again and copy less files/folders to its root folder than you did last time. If it does not help, keep reformatting and decreasing the number of files/folders in the root folder. If this is unacceptable or if it does not help, reformat the outer volume and select a larger cluster size. If it does not help, keep reformatting and increasing the cluster size, until the problem is solved. Alternatively, try creating a hidden volume within an NTFS volume.

Problem:
One of the following problems occurs:
  • A VeraCrypt volume cannot be mounted.
  • NTFS VeraCrypt volumes cannot be created.
In addition, the following error may be reported: "The process cannot access the file because it is being used by another process."
Probable Cause:
This is probably caused by an interfering application. Note that this is not a bug in VeraCrypt. The operating system reports to VeraCrypt that the device is locked for an exclusive access by an application (so VeraCrypt is not allowed to access it).
Possible Solution:
It usually helps to disable or uninstall the interfering application, which is usually an anti-virus utility, a disk management application, etc.

Problem:
In the VeraCrypt Boot Loader screen, I'm trying to type my password and/or pressing other keys but the VeraCrypt boot loader is not responding.
Probable Cause:
You have a USB keyboard (not a PS/2 keyboard) and pre-boot support for USB keyboards is disabled in your BIOS settings.
Possible Solution:
You need to enable pre-boot support for USB keyboards in your BIOS settings. To do so, follow the below steps:
Restart your computer, press F2 or Delete (as soon as you see a BIOS start-up screen), and wait until a BIOS configuration screen appears. If no BIOS configuration screen appears, restart (reset) the computer again and start pressing F2 or Delete repeatedly as soon as you restart (reset) the computer. When a BIOS configuration screen appears, enable pre-boot support for USB keyboards. This can typically be done by selecting:Advanced> 'USB Configuration' > 'Legacy USB Support' (or 'USB Legacy') >Enabled. (Note that the word 'legacy' is in fact misleading, because pre-boot components of modern versions of MS Windows require this option to be enabled to allow user interaction/control.) Then save the BIOS settings (typically by pressing F10) and restart your computer. For more information, please refer to the documentation for your BIOS/motherboard or contact your computer vendor's technical support team for assistance.

Problem:
After the system partition/drive is encrypted, the computer cannot boot after it is restarted (it is also impossible to enter the BIOS configuration screen).
Probable Cause:
A bug in the BIOS of your computer.
Possible Solutions:

Follow these steps:

  1. Disconnect the encrypted drive.
  2. Connect an unencrypted drive with an installed operating system (or install it on the drive).
  3. Upgrade the BIOS.
  4. If it does not help, please report this bug to the manufacturer or vendor of the computer.

OR

  • If the BIOS/motherboard/computer manufacturer/vendor does not provide any updates that resolve the issue and you use Windows 7 or later and there is an extra boot partition (whose size is less than 1 GB) on the drive, you can try reinstalling Windows without this extra boot partition (to work around a bug in the BIOS).

Problem:
One of the following problems occurs:
  • After the pre-boot authentication password is entered during the system encryption pretest, the computer hangs (after the message 'Booting...' is displayed).
  • When the system partition/drive is encrypted (partially or fully) and the system is restarted for the first time since the process of encryption of the system partition/drive started, the computer hangs after you enter the pre-boot authentication password (after the message 'Booting...' is displayed).
  • After the hidden operating system is cloned and the password for it entered, the computer hangs (after the message 'Booting...' is displayed).
Probable Cause:
A bug in the BIOS of your computer.
Possible Solution:
  • Upgrade your BIOS (for information on how to do so, please refer to the documentation for your BIOS/motherboard or contact your computer vendor's technical support team for assistance).
  • Use a different motherboard model/brand.
  • If the BIOS/motherboard/computer manufacturer/vendor does not provide any updates that resolve the issue and you use Windows 7 or later and there is an extra boot partition (whose size is less than 1 GB) on the drive, you can try reinstalling Windows without this extra boot partition (to work around a bug in the BIOS).

Problem:
When trying to encrypt the system partition/drive, during the pretest, the VeraCrypt Boot Loader always reports that the pre-boot authentication password I entered is incorrect (even though I'm sure it is correct).
Possible Causes:
  • Different state of the Num Lock and/or Caps Lock key
  • Data corruption
Possible Solution:
  1. When you set a pre-boot authentication password, remember whether theNum Lock and Caps Lock keys are on or off (depending on the manufacturer, the keys may have different labels, such asNum LK). Note: You can change the state of each of the keys as desired before you set the password, but you need to remember the states.
  2. When you enter the password in the VeraCrypt Boot Loader screen, make sure the state of each of the keys is the same as when you set the password.
Note: For other possible solutions to this problem, see the other sections of this chapter.

Problem:
When the system partition/drive is encrypted, the operating system 'freezes' for approx. 10-60 seconds every 5-60 minutes (100% CPU usage may co-occur).
Probable Cause:
A CPU and/or motherboard issue.
Possible Solutions:
  • Try disabling all power-saving-related features (including any special CPU enhanced halt functions) in the BIOS settings and in the 'Power Options' Windows control panel.
  • Replace the processor with a different one (different type and/or brand).
  • Replace the motherboard with a different one (different type and/or brand).

Problem:
When mounting or dismounting a VeraCrypt volume, the system crashes (a 'blue screen' error screen appears or thecomputer abruptly restarts).
OR
Since I installed VeraCrypt, the operating system has been crashing frequently.
Possible Causes:
  • A bug in a third-party application (e.g. antivirus, system "tweaker", driver, etc.)
  • A bug in VeraCrypt
  • A bug in Windows or a malfunctioning hardware component
Possible Solutions:
  • Try disabling any antivirus tools, system "tweakers", and any other similar applications. If it does not help, try uninstalling them and restarting Windows.

    If the problem persists, run VeraCrypt and select Help> 'Analyze a System Crash' shortly after the system crashes or restarts. VeraCrypt will then analyze crash dump files that Windows automatically created when it crashed (if any). If VeraCrypt determines that a bug in a third party driver is likely to have caused the crash, it will show the name and provider of the driver (note that updating or uninstalling the driver might resolve the issue). Whatever the results, you will be able to choose to send us essential information about the system crash to help us determine whether it was caused by a bug in VeraCrypt.

Problem:
On Windows 7/Vista (and possibly later versions), the Microsoft Windows Backup tool cannot be used to backup data to a non-system VeraCrypt Volume.
Cause:
A bug in the Windows Backup tool.
Possible Solution:
  1. Mount the VeraCrypt volume to which you want to back up data.
  2. Right-click a folder located on the volume (or right-click its drive letter in the 'Computer' list) and select an item from the 'Share with' submenu (on Windows Vista, select 'Share').
  3. Follow the instructions to share the folder with your user account.
  4. In the Windows Backup tool, select the shared folder (the network location/path) as the destination.
  5. Start the backup process.
Note: The above solution does not apply to the Starter andHome editions of Windows 7 (and possibly later versions).

Problem:
The label of a filesystem in a VeraCrypt volume cannot be changed from within the 'Computer' window under Windows Vista or a later version of Windows.
Cause:
A Windows issue causes the label to be written only to the Windows registry file, instead of being written to the filesystem.
Possible Solutions:
  • Right-click the mounted volume in the 'Computer' window, selectProperties, and enter a new label for the volume.

Problem:
I cannot encrypt a partition/device because VeraCrypt Volume Creation Wizard says it is in use.
Possible Solution:
Close, disable, or uninstall all programs that might be using the partition/device in any way (for example an anti-virus utility). If it does not help, right-click the 'Computer' (or 'My Computer') icon on your desktop and select Manage -> Storage-> Disk Management. Then right-click the partition that you want to encrypt, and clickChange Drive Letter and Paths. Then click Remove and OK. Restart the operating system.

Problem:
When creating a hidden volume, the Wizard reports that the outer volume cannot be locked.
Probable Cause:
The outer volume contains files being used by one or more applications.
Possible Solution:
Close all applications that are using files on the outer volume. If it does not help, try disabling or uninstalling any anti-virus utility you use and restarting the system subsequently.

Problem:
When accessing a file-hosted container shared over a network, you receive one or both of the following error messages:
"Not enough server storage is available to process this command." and/or,
"Not enough memory to complete transaction."
Probable Cause:
IRPStackSize in the Windows registry may have been set to a too small value.
Possible Solution:
Locate the IRPStackSize key in the Windows registry and set it to a higher value. Then restart the system. If the key does not exist in the Windows registry, create it atHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and set its value to 16 or higher. Then restart the system. For more information, see: http://support.microsoft.com/kb/285089/ and http://support.microsoft.com/kb/177078/





  See also: Known Issues & Limitations,  Incompatibilities

Commented Unassigned: >4GB files on outer container. [18]

$
0
0
When formatting for a hidden partition the user is prompted whether to allow >4GB files on the hidden partition but is not asked for the outer partition. I'd like to have a virtualbox VM folder on an outer partition but it gets truncated.


Comments: During the creating of the outer partition, you have the possibility to select NTFS as the file system in the "Volume Format" window. By default, it is set to FAT in order to save space for the hidden volume but the user can select NTFS if he needs to store files > 4GB. You certainly didn't pay attention to this option during the creation process. The drawback of selecting NTFS for the outer volume is that the maximum available size of the hidden volume can be very small. This is explained in the FAQ at the following link: [https://veracrypt.codeplex.com/wikipage?title=Troubleshooting#hidden_volume_small_max_size](https://veracrypt.codeplex.com/wikipage?title=Troubleshooting#hidden_volume_small_max_size) Do you confirm that you didn't select NTFS for the outer volume?

Released: VeraCrypt version 1.0e (Sep 04, 2014)

$
0
0
Changes between 1.0d and 1.0e (04 September 2014) :
  • Correct most of the security vulnerabilities reported by the Open Crypto Audit Project.
  • Correct security issues detected by Static Code Analysis, mainly under Windows.
  • Correct issue of unresponsiveness when changing password/key file of a volume. Reduce overall time taken for creating encrypted volume/partition.
  • Minor fixes (look at git history for more details).

Updated Release: VeraCrypt version 1.0e (sept. 04, 2014)

$
0
0
Changes between 1.0d and 1.0e (04 September 2014) :
  • Correct most of the security vulnerabilities reported by the Open Crypto Audit Project.
  • Correct security issues detected by Static Code Analysis, mainly under Windows.
  • Correct issue of unresponsiveness when changing password/key file of a volume. Reduce overall time taken for creating encrypted volume/partition.
  • Minor fixes (look at git history for more details).

Released: VeraCrypt version 1.0f Beta (Oct 26, 2014)

$
0
0

This beta version of VeraCrypt 1.0f is for testing purposes only

Changes between 1.0e and 1.0f-BETA (26 Octobre 2014) :
  • All OSs:
    • Add support for SHA-256 for volume encryption.
    • Make SHA-512 the default key derivation algorithm instead of RIPEMD160.
    • Change the order of preference of derivation algorithms : SHA-512 -> Whirlpool -> SHA-256 -> RIPEMD160
  • MacOSX:
    • Implement support for hard drives with a large sector size (> 512).
    • Link against new wxWidgets version 3.0.2
  • Linux:
    • Add support of NTFS formatting of volumes.
    • Correct issue on opening of the user guide PDF
    • Better support for hard drives with a large sector size (> 512).
    • Link against new wxWidgets version 3.0.2
  • Windows:
    • Security: fix vulnerability in bootloader detected by Open Crypto Audit and make it more robust.
    • Add support for SHA-256 in system boot encryption.
    • Various optimizations in bootloader.
    • Complete fix of ShellExecute security issue.
    • Kernel driver: check that the password length received from bootloader is less or equal to 64.

Updated Release: VeraCrypt version 1.0f Beta (oct. 26, 2014)

$
0
0

This beta version of VeraCrypt 1.0f is for testing purposes only

Changes between 1.0e and 1.0f-BETA (26 Octobre 2014) :
  • All OSs:
    • Add support for SHA-256 for volume encryption.
    • Make SHA-512 the default key derivation algorithm instead of RIPEMD160.
    • Change the order of preference of derivation algorithms : SHA-512 -> Whirlpool -> SHA-256 -> RIPEMD160
  • MacOSX:
    • Implement support for hard drives with a large sector size (> 512).
    • Link against new wxWidgets version 3.0.2
  • Linux:
    • Add support of NTFS formatting of volumes.
    • Correct issue on opening of the user guide PDF
    • Better support for hard drives with a large sector size (> 512).
    • Link against new wxWidgets version 3.0.2
  • Windows:
    • Security: fix vulnerability in bootloader detected by Open Crypto Audit and make it more robust.
    • Add support for SHA-256 in system boot encryption.
    • Various optimizations in bootloader.
    • Complete fix of ShellExecute security issue.
    • Kernel driver: check that the password length received from bootloader is less or equal to 64.

Updated Wiki: Hidden Volume

$
0
0

Hidden Volume

It may happen that you are forced by somebody to reveal the password to an encrypted volume. There are many situations where you cannot refuse to reveal the password (for example, due to extortion). Using a so-called hidden volume allows you to solve such situations without revealing the password to your volume.
The layout of a standard VeraCrypt volume before and after a hidden volume was created within it.
The layout of a standard VeraCrypt volume before and after a hidden volume was created within it.

The principle is that a VeraCrypt volume is created within another VeraCrypt volume (within the free space on the volume). Even when the outer volume is mounted, it should be impossible to prove whether there is a hidden volume within it or not*, because free space on any VeraCrypt volume is always filled with random data when the volume is created** and no part of the (dismounted) hidden volume can be distinguished from random data. Note that VeraCrypt does not modify the file system (information about free space, etc.) within the outer volume in any way.

The password for the hidden volume must be substantially different from the password for the outer volume. To the outer volume, (before creating the hidden volume within it) you should copy some sensitive-looking files that you actually do NOT want to hide. These files will be there for anyone who would force you to hand over the password. You will reveal only the password for the outer volume, not for the hidden one. Files that really are sensitive will be stored on the hidden volume.
A hidden volume can be mounted the same way as a standard VeraCrypt volume: ClickSelect File or Select Deviceto select the outer/host volume (important: make sure the volume is not mounted). Then click Mount, and enter the password for the hidden volume. Whether the hidden or the outer volume will be mounted is determined by the entered password (i.e., when you enter the password for the outer volume, then the outer volume will be mounted; when you enter the password for the hidden volume, the hidden volume will be mounted).
VeraCrypt first attempts to decrypt the standard volume header using the entered password. If it fails, it loads the area of the volume where a hidden volume header can be stored (i.e. bytes 65536–131071, which contain solely random data when there is no hidden volume within the volume) to RAM and attempts to decrypt it using the entered password. Note that hidden volume headers cannot be identified, as they appear to consist entirely of random data. If the header is successfully decrypted (for information on how VeraCrypt determines that it was successfully decrypted, see the section Encryption Scheme), the information about the size of the hidden volume is retrieved from the decrypted header (which is still stored in RAM), and the hidden volume is mounted (its size also determines its offset).
A hidden volume can be created within any type of VeraCrypt volume, i.e., within a file-hosted volume or partition/device-hosted volume (requires administrator privileges). To create a hidden VeraCrypt volume, click onCreate Volume in the main program window and selectCreate a hidden VeraCrypt volume. The Wizard will provide help and all information necessary to successfully create a hidden VeraCrypt volume.
When creating a hidden volume, it may be very difficult or even impossible for an inexperienced user to set the size of the hidden volume such that the hidden volume does not overwrite data on the outer volume. Therefore, the Volume Creation Wizard automatically scans the cluster bitmap of the outer volume (before the hidden volume is created within it) and determines the maximum possible size of the hidden volume.***
If there are any problems when creating a hidden volume, refer to the chapter Troubleshooting for possible solutions.


Note that it is also possible to create and boot an operating system residing in a hidden volume (see the section Hidden Operating System).

* Provided that all the instructions in the VeraCrypt Volume Creation Wizard have been followed and provided that the requirements and precautions listed in the subsection Security Requirements and Precautions Pertaining to Hidden Volumes are followed.
** Provided that the optionsQuick Format and Dynamic are disabled and provided that the volume does not contain a filesystem that has been encrypted in place (VeraCrypt does not allow the user to create a hidden volume within such a volume). For information on the method used to fill free volume space with random data, see chapter Technical Details, section VeraCrypt Volume Format Specification.
*** The wizard scans the cluster bitmap to determine the size of the uninterrupted area of free space (if there is any) whose end is aligned with the end of the outer volume. This area accommodates the hidden volume and therefore the size of this area limits the maximum possible size of the hidden volume. On Linux and Mac OS X, the wizard actually does not scan the cluster bitmap, but the driver detects any data written to the outer volume and uses their position as previously described.

 

Next Section >>

Commented Unassigned: >4GB files on outer container. [18]

$
0
0
When formatting for a hidden partition the user is prompted whether to allow >4GB files on the hidden partition but is not asked for the outer partition. I'd like to have a virtualbox VM folder on an outer partition but it gets truncated.


Comments: Since there was no indication concerning Linux in the first post, I supposed it was about Windows. It's not easy to analyze the context of an issue without details about the version and platform used, and I receive so many false issues that consume a lot of time. I'm sorry if you felt attacked by my comment, it was done because Windows was on my mind and it happens often to users to miss this configuration part of the filesystem of the outer volume. I hope you understand the context of this comment and that it was not a personal attack. In the future, I'll always ask for detailed information concerning the version, platform and hardware configuration before further analysis. This will avoid any confusion or mix-ups. Concerning your issue, indeed under Linux it is not possible to choose the filesystem using the GUI because it is always formatted as FAT. This is done this way because of we need to be able to scan the cluster bitmap of the outer volume in order to determine the maximum allowed size for the hidden volume and we don't know how to do that with filesystems other than FAT on Linux. On Windows, we can also scan the cluster bitmap of NTFS filesystems thanks to specific Windows APIs. The documentation explains the need for such scan (you can [look here](https://veracrypt.codeplex.com/wikipage?title=Hidden%20Volume#hidden_volume_size_issue)). It is almost impossible to manually calculate the correct maximum size of the hidden volume that would ensure that data will not be overwritten. From here, we have two possibilities: 1. Implement the manual scan of cluster bitmaps of other filesystems like Ext3/Ext4 or even NTFS. This is not a easy task and we welcome any contribution on this. The method to modify is __CoreBase::GetMaxHiddenVolumeSize__ in src/Core/CoreBase.cpp ([link to the code](https://sourceforge.net/p/veracrypt/code/ci/master/tree/src/Core/CoreBase.cpp#l130)). 2. Offer the possibility to the user to select any filesystem for the outer volume and let him choose the maximum size of the hidden volume if the selected filesystem is different from FAT. In this, there is a big chance that the value entered will wrong and that data will be overwritten but we can put a warning about this. The second is the easiest way but the data loss risk exist and even if we put a warning about it, most users will find unacceptable. Any thoughts on this? Thank you for bringing up this issue.

New Post: Auto Close Pop Up

$
0
0
OK Thank you for trying :)

It would be a useful feature, if you ever find a way it would be great if you could add it. However for now there are more important things for VeraCrypt :)

Updated Wiki: FAQ

$
0
0

F r e q u e n t l y   A s k e d   Q u e s t i o n s

Last Updated November 14th, 2014
This document is not guaranteed to be error-free and is provided "as is" without warranty of any kind. For more information, see Disclaimers.
Can TrueCrypt and VeraCrypt be running on the same machine?
Yes. There are no conflicts between TrueCrypt and VeraCrypt, thus they can be installed and used on the same machine.
What's the difference between TrueCrypt and VeraCrypt?
VeraCrypt adds enhanced security to the algorithms used for system and partitions encryption making it immune to new developments in brute-force attacks.
It also solves many vulnerabilities and security issues found in TrueCrypt. The following post describes parts of the major enhancements and corrections done so far:https://veracrypt.codeplex.com/discussions/569777#PostContent_1313325
As an example, when the system partition is encrypted, TrueCrypt uses PBKDF2-RIPEMD160 with 1000 iterations whereas in VeraCrypt we use327661. And for standard containers and other partitions, TrueCrypt uses at most 2000 iterations but VeraCrypt uses655331 for RIPEMD160 and 500000 iterations for SHA-2 and Whirlpool.
This enhanced security adds some delay only to the opening of encrypted partitions without any performance impact to the application use phase. This is acceptable to the legitimate owner but it makes it much more harder for an attacker to gain access to the encrypted data.

I forgot my password – is there any way ('backdoor') to recover the files from my VeraCrypt volume?
We have not implemented any 'backdoor' in VeraCrypt (and will never implement any even if asked to do so by a government agency), because it would defeat the purpose of the software. VeraCrypt does not allow decryption of data without knowing the correct password or key. We cannot recover your data because we do not know and cannot determine the password you chose or the key you generated using VeraCrypt. The only way to recover your files is to try to "crack" the password or the key, but it could take thousands or millions of years (depending on the length and quality of the password or keyfiles, on the software/hardware performance, algorithms, and other factors). Back in 2010, there were news about the FBI failing to decrypt a TrueCrypt volume after a year of trying. While we can't verify if this is true or just a "psy-op" stunt, in VeraCrypt we have increased the security of the key derivation to a level where any brute-force of the password is virtually impossible, provided that all security requirements are provided.

Is there a "Quick Start Guide" or some tutorial for beginners?
Yes. The first chapter, Beginner's Tutorial, in the VeraCrypt User Guide contains screenshots and step-by-step instructions on how to create, mount, and use a VeraCrypt volume.

Can I encrypt a partition/drive where Windows is installed?
Yes, see the chapter System Encryption in the VeraCrypt User Guide.

Can I directly play a video (.avi, .mpg, etc.) stored on a VeraCrypt volume?
Yes, VeraCrypt-encrypted volumes are like normal disks. You provide the correct password (and/or keyfile) and mount (open) the VeraCrypt volume. When you double click the icon of the video file, the operating system launches the application associated with the file type – typically a media player. The media player then begins loading a small initial portion of the video file from the VeraCrypt-encrypted volume to RAM (memory) in order to play it. While the portion is being loaded, VeraCrypt is automatically decrypting it (in RAM). The decrypted portion of the video (stored in RAM) is then played by the media player. While this portion is being played, the media player begins loading another small portion of the video file from the VeraCrypt-encrypted volume to RAM (memory) and the process repeats.

The same goes for video recording: Before a chunk of a video file is written to a VeraCrypt volume, VeraCrypt encrypts it in RAM and then writes it to the disk. This process is called on-the-fly encryption/decryption and it works for all file types (not only for video files).

Will VeraCrypt be open-source and free forever?
Yes, it will. We will never create a commercial version of VeraCrypt, as we believe in open-source and free security software.

Is it possible to donate to the VeraCrypt project?
Yes. You can use the donation buttons at https://veracrypt.codeplex.com.

Why is VeraCrypt open-source? What are the advantages?
As the source code for VeraCrypt is publicly available, independent researchers can verify that the source code does not contain any security flaw or secret 'backdoor'. If the source code were not available, reviewers would need to reverse-engineer the executable files. However, analyzing and understanding such reverse-engineered code is so difficult that it is practicallyimpossible to do (especially when the code is as large as the VeraCrypt code).

Remark: A similar problem also affects cryptographic hardware (for example, a self-encrypting storage device). It is very difficult to reverse-engineer it to verify that it does not contain any security flaw or secret 'backdoor'.

VeraCrypt is open-source, but has anybody actually reviewed the source code?
Yes. In fact, the source code is constantly being reviewed by many independent researchers and users. We know this because many bugs and several security issues have been discovered by independent researchers while reviewing the source code. Moreover, VeraCrypt is based on TrueCrypt which was independently audited by the Open Crypto Audit project and all the major issues discovered by this audit were fixed in VeraCrypt. The report of the audit can be found here. For a list of the issues that were fixed in VeraCrypt, you click here

As VeraCrypt is open-source software, independent researchers can verify that the source code does not contain any security flaw or secret 'backdoor'. Can they also verify that the official executable files were built from the published source code and contain no additional code?
Yes, they can. In addition to reviewing the source code, independent researchers can compile the source code and compare the resulting executable files with the official ones. They may find some differences (for example, timestamps or embedded digital signatures) but they can analyze the differences and verify that they do not form malicious code.

How can I use VeraCrypt on a USB flash drive?
You have two options:
  1. Encrypt the entire USB flash drive. However, you will not be able run VeraCrypt from the USB flash drive.
    Note: Windows does not support multiple partitions on USB flash drives.
  2. Create a VeraCrypt file container on the USB flash drive (for information on how to do so, see the chapterBeginner's Tutorial, in the VeraCrypt User Guide). If you leave enough space on the USB flash drive (choose an appropriate size for the VeraCrypt container), you will also be able to store VeraCrypt on the USB flash drive (along with the container – notin the container) and you will be able to run VeraCrypt from the USB flash drive (see also the chapter Portable Mode in the VeraCrypt User Guide).

Does VeraCrypt also encrypt file names and folder names?
Yes. The entire file system within a VeraCrypt volume is encrypted (including file names, folder names, and contents of every file). This applies to both types of VeraCrypt volumes – i.e., to file containers (virtual VeraCrypt disks) and to VeraCrypt-encrypted partitions/devices.

Does VeraCrypt use parallelization?
Yes. Increase in encryption/decryption speed is directly proportional to the number of cores/processors your computer has. For more information, please see the chapter Parallelization in the documentation.

Can data be read from and written to an encrypted volume/drive as fast as if the drive was not encrypted?
Yes, since VeraCrypt uses pipelining and parallelization. For more information, please see the chapters Pipelining and Parallelization in the documentation.

Does VeraCrypt support hardware-accelerated encryption?
Yes. For more information, please see the chapter Hardware Acceleration in the documentation.

Is it possible to boot Windows installed in a hidden VeraCrypt volume?
Yes, it is. For more information, please see the section Hidden Operating System in the documentation.

Will I be able to mount my VeraCrypt volume (container) on any computer?
Yes, VeraCrypt volumes are independent of the operating system. You will be able to mount your VeraCrypt volume on any computer on which you can run VeraCrypt (see also the question 'Can I use VeraCrypt on Windows if I do not have administrator privileges?').

Can I unplug or turn off a hot-plug device (for example, a USB flash drive or USB hard drive) when there is a mounted VeraCrypt volume on it?
Before you unplug or turn off the device, you should always dismount the VeraCrypt volume in VeraCrypt first, and then perform the 'Eject' operation if available (right-click the device in the 'Computer' or 'My Computer' list), or use the 'Safely Remove Hardware' function (built in Windows, accessible via the taskbar notification area). Otherwise, data loss may occur.

What is a hidden operating system?

What is plausible deniability?
See the chapter Plausible Deniability in the documentation.

Will I be able to mount my VeraCrypt partition/container after I reinstall or upgrade the operating system?
Yes, VeraCrypt volumes are independent of the operating system. However, you need to make sure your operating system installer does not format the partition where your VeraCrypt volume resides.

Note: If the system partition/drive is encrypted and you want to reinstall or upgrade Windows, you need to decrypt it first (selectSystem> Permanently Decrypt System Partition/Drive). However, a running operating system can beupdated (security patches, service packs, etc.) without any problems even when the system partition/drive is encrypted.

Can I upgrade from an older version of VeraCrypt to the latest version without any problems?
Generally, yes. However, before upgrading, please read the release notes for all versions of VeraCrypt that have been released since your version was released. If there are any known issues or incompatibilities related to upgrading from your version to a newer one, they will be listed in the release notes.

Can I upgrade VeraCrypt if the system partition/drive is encrypted or do I have to decrypt it first?
Generally, you can upgrade to the latest version without decrypting the system partition/drive (just run the VeraCrypt installer and it will automatically upgrade VeraCrypt on the system). However, before upgrading, please read the release notes for all versions of VeraCrypt that have been released since your version was released. If there are any known issues or incompatibilities related to upgrading from your version to a newer one, they will be listed in the release notes. Note that this FAQ answer is also valid for users of a hidden operating system. Also note that you cannot downgrade VeraCrypt if the system partition/drive is encrypted.

I use pre-boot authentication. Can I prevent a person (adversary) that is watching me start my computer from knowing that I use VeraCrypt?
Yes. To do so, boot the encrypted system, start VeraCrypt, select Settings> System Encryption, enable the option 'Do not show any texts in the pre-boot authentication screen' and clickOK. Then, when you start the computer, no texts will be displayed by the VeraCrypt boot loader (not even when you enter the wrong password). The computer will appear to be "frozen" while you can type your password. It is, however, important to note that if the adversary can analyze the content of the hard drive, he can still find out that it contains the VeraCrypt boot loader.

I use pre-boot authentication. Can I configure the VeraCrypt Boot Loader to display only a fake error message?
Yes. To do so, boot the encrypted system, start VeraCrypt, select Settings> System Encryption, enable the option 'Do not show any texts in the pre-boot authentication screen' and enter the fake error message in the corresponding field (for example, the "Missing operating system" message, which is normally displayed by the Windows boot loader if it finds no Windows boot partition). It is, however, important to note that if the adversary can analyze the content of the hard drive, he can still find out that it contains the VeraCrypt boot loader.

Can I configure VeraCrypt to mount automatically whenever Windows starts a non-system VeraCrypt volume that uses the same password as my system partition/drive (i.e. my pre-boot authentication password)?
Yes. To do so, follow these steps:
  1. Mount the volume (to the drive letter to which you want it to be mounted every time).
  2. Right-click the mounted volume in the drive list in the main VeraCrypt window and select 'Add to System Favorites'.
  3. The System Favorites Organizer window should appear now. In this window, enable the option 'Mount system favorite volumes when Windows starts' and clickOK.
For more information, see the chapter System Favorite Volumes.

Can a volume be automatically mounted whenever I log on to Windows?
Yes. To do so, follow these steps:
  1. Mount the volume (to the drive letter to which you want it to be mounted every time).
  2. Right-click the mounted volume in the drive list in the main VeraCrypt window and select 'Add to Favorites'.
  3. The Favorites Organizer window should appear now. In this window, enable the option 'Mount selected volume upon logon' and clickOK.
Then, when you log on to Windows, you will be asked for the volume password (and/or keyfiles) and if it is correct, the volume will be mounted.

Alternatively, if the volumes are partition/device-hosted and if you do not need to mount them to particular drive letters every time, you can follow these steps:
  1. Select Settings> Preferences. The Preferences window should appear now.
  2. In the section 'Actions to perform upon logon to Windows', enable the option 'Mount all devices-hosted VeraCrypt volumes' and clickOK.
Note: VeraCrypt will not prompt you for a password if you have enabled caching of the pre-boot authentication password (Settings> 'System Encryption') and the volumes use the same password as the system partition/drive.

Can a volume be automatically mounted whenever its host device gets connected to the computer?
Yes. For example, if you have a VeraCrypt container on a USB flash drive and you want VeraCrypt to mount it automatically when you insert the USB flash drive into the USB port, follow these steps:
  1. Mount the volume (to the drive letter to which you want it to be mounted every time).
  2. Right-click the mounted volume in the drive list in the main VeraCrypt window and select 'Add to Favorites'.
  3. The Favorites Organizer window should appear now. In this window, enable the option 'Mount selected volume when its host device gets connected' and clickOK.
Then, when you insert the USB flash drive into the USB port, you will be asked for the volume password (and/or keyfiles) (unless it is cached) and if it is correct, the volume will be mounted.

Note: VeraCrypt will not prompt you for a password if you have enabled caching of the pre-boot authentication password (Settings> 'System Encryption') and the volume uses the same password as the system partition/drive.

Can my pre-boot authentication password be cached so that I can use it mount non-system volumes during the session?
Yes. Select Settings> 'System Encryption' and enable the following option: 'Cache pre-boot authentication password in driver memory'.

I live in a country that violates basic human rights of its people. Is it possible to use VeraCrypt without leaving any 'traces' on unencrypted Windows?
Yes. This can be achieved by running VeraCrypt in portable mode under BartPE or in a similar environment. BartPE stands for "Bart's Preinstalled Environment", which is essentially the Windows operating system prepared in a way that it can be entirely stored on and booted from a CD/DVD (registry, temporary files, etc., are stored in RAM – hard drive is not used at all and does not even have to be present). The freeware Bart's PE Builder can transform a Windows XP installation CD into a BartPE CD. Note that you do not even need any special VeraCrypt plug-in for BartPE. Follow these steps:
  1. Create a BartPE CD and boot it. (Note: You must perform each of the following steps from within BartPE.)
  2. Download the VeraCrypt self-extracting package to the RAM disk (which BartPE automatically creates).

    Note: If the adversary can intercept data you send or receive over the Internet and you need to prevent the adversary from knowing you downloaded VeraCrypt, consider downloading it viaI2P, Tor, or a similar anonymizing network.
  3. Verify the digital signatures of the downloaded file (see this section of the documentation for more information).
  4. Run the downloaded file, and select Extract (instead ofInstall) on the second page of the VeraCrypt Setup wizard. Extract the contents to the RAM disk.
  5. Run the file VeraCrypt.exe from the RAM disk.
Note: You may also want to consider creating a hidden operating system (see the section Hidden Operating System in the documentation). See also the chapter Plausible Deniability.

Can I encrypt my system partition/drive if I don't have a US keyboard?
Yes, VeraCrypt supports all keyboard layouts.

Can I save data to the decoy system partition without risking damage to the hidden system partition?
Yes. You can write data to the decoy system partition anytime without any risk that the hidden volume will get damaged (because the decoy system isnot installed within the same partition as the hidden system). For more information, see the section Hidden Operating System in the documentation.

Can I use VeraCrypt on Windows if I do not have administrator privileges?

Does VeraCrypt save my password to a disk?
No.

How does VeraCrypt verify that the correct password was entered?
See the section Encryption Scheme (chapter Technical Details) in the documentation.

Can I encrypt a partition/drive without losing the data currently stored on it?
Yes, but the following conditions must be met:
  • If you want to encrypt an entire system drive (which may contain multiple partitions) or a system partition (in other words, if you want to encrypt a drive or partition where Windows is installed), you can do so provided that you use VeraCrypt 5.0 or later and that you use Windows XP or a later version of Windows (such as Windows 7) (select 'System' > 'Encrypt System Partition/Drive' and then follow the instructions in the wizard).
  • If you want to encrypt a non-system partition in place, you can do so provided that it contains an NTFS filesystem, that you use VeraCrypt 6.1 or later, and that you use Windows Vista or a later version of Windows (for example, Windows 7)(click 'Create Volume' > 'Encrypt a non-system partition' > 'Standard volume' > 'Select Device' > 'Encrypt partition in place' and then follow the instructions in the wizard).

Can I run VeraCrypt if I don't install it?
Yes, see the chapter Portable Mode in the VeraCrypt User Guide.

Some encryption programs use TPM to prevent attacks. Will VeraCrypt use it too?
No. Those programs use TPM to protect against attacks that require the attacker to have administrator privileges, or physical access to the computer, and the attacker needs you to use the computer after such an access.However, if any of these conditions is met, it is actually impossible to secure the computer (see below) and, therefore, you must stop using it (instead of relying on TPM).

If the attacker has administrator privileges, he can, for example, reset the TPM, capture the content of RAM (containing master keys) or content of files stored on mounted VeraCrypt volumes (decrypted on the fly), which can then be sent to the attacker over the Internet or saved to an unencrypted local drive (from which the attacker might be able to read it later, when he gains physical access to the computer).

If the attacker can physically access the computer hardware (and you use it after such an access), he can, for example, attach a malicious component to it (such as a hardware keystroke logger) that will capture the password, the content of RAM (containing master keys) or content of files stored on mounted VeraCrypt volumes (decrypted on the fly), which can then be sent to the attacker over the Internet or saved to an unencrypted local drive (from which the attacker might be able to read it later, when he gains physical access to the computer again).

The only thing that TPM is almost guaranteed to provide is a false sense of security (even the name itself, "Trusted Platform Module", is misleading and creates a false sense of security). As for real security, TPM is actually redundant (and implementing redundant features is usually a way to create so-called bloatware).

For more information, please see the sections Physical Security and Malware in the documentation.

Do I have to dismount VeraCrypt volumes before shutting down or restarting Windows?
No. VeraCrypt automatically dismounts all mounted VeraCrypt volumes on system shutdown/restart.

Which type of VeraCrypt volume is better – partition or file container?
File containers are normal files so you can work with them as with any normal files (file containers can be, for example, moved, renamed, and deleted the same way as normal files). Partitions/drives may be better as regards performance. Note that reading and writing to/from a file container may take significantly longer when the container is heavily fragmented. To solve this problem, defragment the file system in which the container is stored (when the VeraCrypt volume is dismounted).

What's the recommended way to back up a VeraCrypt volume?

What will happen if I format a VeraCrypt partition?

Is it possible to change the file system of an encrypted volume?
Yes, when mounted, VeraCrypt volumes can be formatted as FAT12, FAT16, FAT32, NTFS, or any other file system. VeraCrypt volumes behave as standard disk devices so you can right-click the device icon (for example in the 'Computer' or 'My Computer' list) and select 'Format'. The actual volume contents will be lost. However, the whole volume will remain encrypted. If you format a VeraCrypt-encrypted partition when the VeraCrypt volume that the partition hosts is not mounted, then the volume will be destroyed, and the partition will not be encrypted anymore (it will be empty).

Is it possible to mount a VeraCrypt container that is stored on a CD or DVD?
Yes. However, if you need to mount a VeraCrypt volume that is stored on a read-only medium (such as a CD or DVD) under Windows 2000, the file system within the VeraCrypt volume must be FAT (Windows 2000 cannot mount an NTFS file system on read-only media).

Is it possible to change the password for a hidden volume?
Yes, the password change dialog works both for standard and hidden volumes. Just type the password for the hidden volume in the 'Current Password' field of the 'Volume Password Change' dialog.
Remark: VeraCrypt first attempts to decrypt the standard volume header and if it fails, it attempts to decrypt the area within the volume where the hidden volume header may be stored (if there is a hidden volume within). In case it is successful, the password change applies to the hidden volume. (Both attempts use the password typed in the 'Current Password' field.)

When I use HMAC-RIPEMD-160, is the size of the header encryption key only 160 bits?
No, VeraCrypt never uses an output of a hash function (nor of a HMAC algorithm) directly as an encryption key. See the section Header Key Derivation, Salt, and Iteration Count in the documentation for more information.

How do I burn a VeraCrypt container larger than 2 GB onto a DVD?

The DVD burning software you use should allow you to select the format of the DVD. If it does, select the UDF format (ISO format does not support files larger than 2 GB).

Can I use tools like chkdsk, Disk Defragmenter, etc. on the contents of a mounted VeraCrypt volume?
Yes, VeraCrypt volumes behave like real physical disk devices, so it is possible to use any filesystem checking/repairing/defragmenting tools on the contents of a mounted VeraCrypt volume.

Does VeraCrypt support 64-bit versions of Windows?
Yes, it does. Note: 64-bit versions of Windows load only drivers that are digitally signed with a digital certificate issued by a certification authority approved for issuing kernel-mode code signing certificates. VeraCrypt complies with this requirement (the VeraCrypt driver is digitally signed with the digital certificate of IDRIX, which was issued by the certification authority Thawte).

Can I mount my VeraCrypt volume under Windows, Mac OS X, and Linux?
Yes, VeraCrypt volumes are fully cross-platform.

Is there a list of all operating systems that VeraCrypt supports?

Is it possible to install an application to a VeraCrypt volume and run it from there?
Yes.

What will happen when a part of a VeraCrypt volume becomes corrupted?
In encrypted data, one corrupted bit usually corrupts the whole ciphertext block in which it occurred. The ciphertext block size used by VeraCrypt is 16 bytes (i.e., 128 bits). The mode of operation used by VeraCrypt ensures that if data corruption occurs within a block, the remaining blocks are not affected. See also the question 'What do I do when the encrypted filesystem on my VeraCrypt volume is corrupted?

What do I do when the encrypted filesystem on my VeraCrypt volume is corrupted?
File system within a VeraCrypt volume may become corrupted in the same way as any normal unencrypted file system. When that happens, you can use filesystem repair tools supplied with your operating system to fix it. In Windows, it is the 'chkdsk' tool. VeraCrypt provides an easy way to use this tool on a VeraCrypt volume: Right-click the mounted volume in the main VeraCrypt window (in the drive list) and from the context menu select 'Repair Filesystem'.

We use VeraCrypt in a corporate/enterprise environment. Is there a way for an administrator to reset a volume password or pre-boot authentication password when a user forgets it (or loses a keyfile)?
Yes. Note that there is no "backdoor" implemented in VeraCrypt. However, there is a way to "reset" volume passwords/keyfiles and pre-boot authentication passwords. After you create a volume, back up its header to a file (selectTools -> Backup Volume Header) before you allow a non-admin user to use the volume. Note that the volume header (which is encrypted with a header key derived from a password/keyfile) contains the master key with which the volume is encrypted. Then ask the user to choose a password, and set it for him/her (Volumes ->Change Volume Password); or generate a user keyfile for him/her. Then you can allow the user to use the volume and to change the password/keyfiles without your assistance/permission. In case he/she forgets his/her password or loses his/her keyfile, you can "reset" the volume password/keyfiles to your original admin password/keyfiles by restoring the volume header from the backup file (Tools ->Restore Volume Header).

Similarly, you can reset a pre-boot authentication password.To create a backup of the master key data (that will be stored on a VeraCrypt Rescue Disk and encrypted with your administrator password), select 'System' > 'Create Rescue Disk'. To set a user pre-boot authentication password, select 'System' > 'Change Password'. To restore your administrator password, boot the VeraCrypt Rescue Disk, select 'Repair Options' > 'Restore key data' and enter your administrator password.
Note: It is not required to burn each VeraCrypt Rescue Disk ISO image to a CD/DVD. You can maintain a central repository of ISO images for all workstations (rather than a repository of CDs/DVDs). For more information see the section Command Line Usage (option /noisocheck).

Can our commercial company use VeraCrypt free of charge?
Provided that you comply with the terms and conditions of the VeraCrypt License, you can install and run VeraCrypt free of charge on an arbitrary number of your computers.

We share a volume over a network. Is there a way to have the network share automatically restored when the system is restarted?
Please see the chapter 'Sharing over Network' in the VeraCrypt User Guide.

It is possible to access a single VeraCrypt volume simultaneously from multiple operating systems (for example, a volume shared over a network)?
Please see the chapter 'Sharing over Network' in the VeraCrypt User Guide.

Can a user access his or her VeraCrypt volume via a network?
Please see the chapter 'Sharing over Network' in the VeraCrypt User Guide.

I encrypted a non-system partition, but its original drive letter is still visible in the 'My Computer' list. When I double click this drive letter, Windows asks if I want to format the drive. Is there a way to hide or free this drive letter?
Yes, to free the drive letter follow these steps:
  1. Right-click the 'Computer' (or 'My Computer') icon on your desktop or in the Start Menu and selectManage. The 'Computer Management' window should appear.
  2. From the list on the left, select 'Disk Management' (within theStorage sub-tree).
  3. Right-click the encrypted partition/device and select Change Drive Letter and Paths.
  4. Click Remove.
  5. If Windows prompts you to confirm the action, click Yes.

When I plug in my encrypted USB flash drive, Windows asks me if I want to format it. Is there a way to prevent that?
Yes, but you will need to remove the drive letter assigned to the device. For information on how to do so, see the question 'I encrypted a non-system partition, but its original drive letter is still visible in the 'My Computer' list.'

How do I remove or undo encryption if I do not need it anymore? How do I permanently decrypt a volume?
Please see the section 'How to Remove Encryption' in the VeraCrypt User Guide.

What will change when I enable the option 'Mount volumes as removable media'?

Is the online documentation available for download as a single file?
Yes, the documentation is contained in the file VeraCrypt User Guide.pdf that is included in all official VeraCrypt distribution packages. Note that you donot have to install VeraCrypt to obtain the PDF documentation. Just run the self-extracting installation package and then selectExtract (instead of Install) on the second page of the VeraCrypt Setup wizard. Also note that when youdo install VeraCrypt, the PDF documentation is automatically copied to the folder to which VeraCrypt is installed, and is accessible via the VeraCrypt user interface (by pressing F1 or choosingHelp> User's Guide).

Do I have to "wipe" free space and/or files on a VeraCrypt volume?
Remark: to "wipe" = to securely erase; to overwrite sensitive data in order to render them unrecoverable.

If you believe that an adversary will be able to decrypt the volume (for example that he will make you reveal the password), then the answer is yes. Otherwise, it is not necessary, because the volume is entirely encrypted.

How does VeraCrypt know which encryption algorithm my VeraCrypt volume has been encrypted with?
Please see the section Encryption Scheme (chapter Technical Details) in the documentation.

I haven't found any answer to my question in the FAQ – what should I do?
Please search the VeraCrypt documentation and website.

Commented Unassigned: >4GB files on outer container. [18]

$
0
0
When formatting for a hidden partition the user is prompted whether to allow >4GB files on the hidden partition but is not asked for the outer partition. I'd like to have a virtualbox VM folder on an outer partition but it gets truncated.


Comments: I assumed all the distro's/architecture's used the same gui but I should have included the info in my original post for clarity. Well Linux has the ability to r/w ntfs but I'm not sure how stable an implementation it is so one possibility is to allow ntfs as a choice. As far as the size to make the inner container....have you considered creating the outer container to max size, creating the inner container with a user selected value of say up to MAX - 10% (or some such) and THEN populate the outer partition, using the protect option, with files? This has the added possibility of allowing you to support any filesystem the user's platform allows. I don't know about typical usage but if I want to have a vm on my encrypted partition that is callable from the host pc then I really need to also be able to have a different vm on the outer container that would boot when the outer password is given for plausible deny-ability. If you build the inner partition while the outer is still empty than various utilities like hdparm, df etc can be used to get the "total free" capacity of the device. I also wondered at the possibility of being able to mount both the inner and the outer container's at the same time....why? Because we need to keep the outer files looking like they are being accessed....if the outer container is mounted and every file shows a time/date stamp of 6 months ago it's also a giveaway for plausible deny-ability. An alternative (and I assume windows has something similar) is to use "touch" to update the date/time stamp on a random percentage of files on the outer container each time the inner container is accessed. You may already be doing this but I've seen other applications such as virtualbox that can use a command like "vboxmanage filename.vdi compact" to shrink a virtual hard disk image by compressing all the space that has been zero filled...if under your current method you were to zero fill the outer container then populate files would it simplify your task of identifying what space was available? The compact command also only shrinks "contiguous free space" and I assume the source is available since it has an open source version.

New Post: Serious memory leak ?

$
0
0
Hi,

I was planning to migrate to Veracrypt, but during copying of data I noticed that I cannot copy data from 1 veracrypt volume to another veracrypt volume. When both are mounted and I'm starting to copy the memory raises in a couple of seconds to 95% of use and basically this causes the system to perform very slowly so I must stop the copy operation. The memory stay on the high level until I dismount the volume, after dismounting the volume the memory is back to a normal level (20%). Any suggestions on what could be wrong ?
One additional finding is that when looking into memory using RAMMAP I can see one of this volumes in "File Summary" tab - even when not mounted and it have a total 5 GB of memory showing in the list - I'm really puzzled why this is showing there..

Image

The issue occurs only when copying data from Veracrypt encrypted volume to some other volume (can be normal, not encrypted volume). The same action - copy from a truecrypt volume cause very little memory use. Really hoping this issue can be solved as I already have some data there which isn't backed up...and seems that I cannot copy it now anywhere..

This is basically doing the same but from truecrypt volume (to veracrypt):
Image

New Post: Serious memory leak ?

$
0
0
Hi,

This has been reported previously on Sourceforge VeraCrypt forum. This is not a memory leak in VeraCrypt but rather a well know issue in Windows.
Here is the link of the discussion: https://sourceforge.net/p/veracrypt/discussion/technical/thread/fb8c352d/ where you can find my answer at the bottom with technical details about a solution.

Thanks for updating us if the solution solves your issue.

Updated Wiki: Journaling File Systems

$
0
0

Journaling File Systems

When a file-hosted VeraCrypt container is stored in a journaling file system (such as NTFS or Ext3), a copy of the VeraCrypt container (or of its fragment) may remain in the free space on the host volume. This may have various security implications. For example, if you change the volume password/keyfile(s) and an adversary finds the old copy or fragment (the old header) of the VeraCrypt volume, he might use it to mount the volume using an old compromised password (and/or using compromised keyfiles using an old compromised password (and/or using compromised keyfiles that were necessary to mount the volume before the volume header was re- encrypted). Some journaling file systems also internally record file access times and other potentially sensitive information. If you need plausible deniability (see section Plausible Deniability), you must not store file-hosted VeraCrypt containers in journaling file systems. To prevent possible security issues related to journaling file systems, do one the following:

  • Use a partition/device-hosted VeraCrypt volume instead of file-hosted.
  • Store the container in a non-journaling file system (for example, FAT32).
Viewing all 7620 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>