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

New Post: Is there a way to make VeraCrypt work on the Raspberry Pi?

March 7, 2015, 4:21 am
$
0
0
Hi,

I wrote a how to article about VeraCrypt on the Raspberry Pi. You need ArchLinux ARM but i'm sure that it would be adaptable to other distributions.

I hope that it can help

Wared
↧
Search

New Post: Lighter encryption / Faster Mount

March 7, 2015, 4:25 am
$
0
0
Mounting encrypted file containers takes some time (maybe 1min) on my PC, and I was wondering if you could add an option to use a faster (possibly less secure) algorithm so that mounting would have better performance.

On my case, I don't really need the encrypted files to be NSA safe, just something that a regular person without advanced hacking knowledge couldn't get into; and that it would be practical enough that I can mount/unmount whenever I need to access the files.
I used to use Securstar's DriveCrypt which was pretty fast, although not free.

Another nice option on Hidden volumes, would be an option to have automatically protected Hidden volumes (or just support multiple (protected) volumes in the same container, selected based on the password) - I would guess this would imply that in this case it would be possible for an expert hacker to identify that the container contains multiple volumes, but I think for many people this feature might be worth the risk (otherwise they can use the current Hidden volume functionality and take care to select the protection option when mounting the container).
↧
↧

New Post: Incorrect Parameter

March 7, 2015, 5:44 am
$
0
0
Excellent work Pulga!

I must correct a mistake I made when I said:
The "Favorite Volumes.xml" file is only created when you successfully add a volume to either Favorites or System Favorites.
.
This is incorrect as Pulga pointed out.

There are two favorite files stored in different directories. See the documentation section VeraCrypt System Files for locations of various files.

Strange that you can use any letter except the D letter. Does Windows Disk Management or Windows Explorer show the D letter assigned?
↧

New Post: Lighter encryption / Faster Mount

March 7, 2015, 6:07 am
$
0
0
Regarding the mount times, Mounir, the developer of VeraCrypt has stated that he will not compromise the security of VeraCrypt for faster mount times.

Instead, Mounir is planning to modify VeraCrypt to allow the user to select a lower iteration count for the hash when the password is 20 or more characters.

You can read Mounir's detailed explanation at this link:

http://tinyurl.com/kssfpvj


Your second suggestion to automatically protect the hidden volumes is not possible. See the documentation on Hidden Volume to understand how VeraCrypt uses the passwords to mount the outer and hidden volumes.


Mounir will need reply to the feasibility of your third request for multiple volumes in the same container.
↧

New Post: Incorrect Parameter

March 7, 2015, 6:08 am
$
0
0
No, I meant, it is possible to assign the D letter, but when I assign D to my second drive, it is not possible to mount it in Veracrypt with the letter D. Therefore I had to choose any other letter.
↧
↧

Updated Wiki: Keyfiles in VeraCrypt

March 7, 2015, 6:52 am
$
0
0

Keyfiles


Keyfile is a file whose content is combined with a password (for information on the method used to combine a keyfile with password, see the section Keyfiles in the chapter Technical Details). Until the correct keyfile is provided, no volume that uses the keyfile can be mounted.
You do not have to use keyfiles. However, using keyfiles has some advantages:
  • May improve protection against brute force attacks (significant particularly if the volume password is not very strong).
  • Allows the use of security tokens and smart cards (see below).
  • Allows multiple users to mount a single volume using different user passwords or PINs. Just give each user a security token or smart card containing the same VeraCrypt keyfile and let them choose their personal password or PIN that will protect their security token or smart card.
  • Allows managing multi-user shared access (all keyfile holders must present their keyfiles before a volume can be mounted).
Any kind of file (for example, .txt, .exe, mp3**, .avi) can be used as a VeraCrypt keyfile (however, we recommend that you prefer compressed files, such as .mp3, .jpg, .zip, etc).

Note that VeraCrypt never modifies the keyfile contents. You can select more than one keyfile; the order does not matter. You can also let VeraCrypt generate a file with random content and use it as a keyfile. To do so, selectTools > Keyfile Generator.
Note: Keyfiles are currently not supported for system encryption.
WARNING: If password caching is enabled, the password cache also contains the processed contents of keyfiles used to successfully mount a volume. Then it is possible to remount the volume even if the keyfile is not available/accessible. To prevent this, click 'Wipe Cache' or disable password caching (for more information, please see the subsection'Settings -> Preferences', item 'Cache passwords in driver memory' in the sectionProgram Menu).

 

Keyfiles Dialog Window

If you want to use keyfiles (i.e. "apply" them) when creating or mounting volumes, or changing passwords, look for the 'Use keyfiles' option and theKeyfiles button below a password input field.
VeraCrypt Keyfiles dialog
These control elements appear in various dialog windows and always have the same functions. Check theUse keyfiles option and click Keyfiles. The keyfile dialog window should appear where you can specify keyfiles (to do so, clickAdd Files or Add Token Files) or keyfile search paths (clickAdd Path).

 

Security Tokens and Smart Cards

VeraCrypt can directly use keyfiles stored on a security token or smart card that complies with the PKCS #11 (2.0 or later) standard [23] and that allows the user to store a file (data object) on the token/card. To use such files as VeraCrypt keyfiles, click Add Token Files (in the keyfile dialog window).
Access to a keyfile stored on a security token or smart card is typically protected by PIN codes, which can be entered either using a hardware PIN pad or via the VeraCrypt GUI. It can also be protected by other means, such as fingerprint readers.
In order to allow VeraCrypt to access a security token or smart card, you need to install a PKCS #11 (2.0 or later) software library for the token or smart card first. Such a library may be supplied with the device or it may be available for download from the website of the vendor or other third parties.
If your security token or smart card does not contain any file (data object) that you could use as a VeraCrypt keyfile, you can use VeraCrypt to import any file to the token or smart card (if it is supported by the device). To do so, follow these steps:
  1. In the keyfile dialog window, click Add Token Files.
  2. If the token or smart card is protected by a PIN, password, or other means (such as a fingerprint reader), authenticate yourself (for example, by entering the PIN using a hardware PIN pad).
  3. The 'Security Token Keyfile' dialog window should appear. In it, click Import Keyfile to Token and then select the file you want to import to the token or smart card.
Note that you can import for example 512-bit keyfiles with random content generated by VeraCrypt (seeTools > Keyfile Generator below).
To close all opened security token sessions, either select Tools> Close All Security Token Sessions or define and use a hotkey combination (Settings>Hot Keys > Close All Security Token Sessions).

 

Keyfile Search Path

By adding a folder in the keyfile dialog window (click Add Path), you specify a keyfile search path. All files found in the keyfile search path* will be used as keyfiles except files that have the Hidden file attribute set.
Important: Note that folders (and files they contain) and hidden files found in a keyfile search path are ignored.
Keyfile search paths are especially useful if you, for example, store keyfiles on a USB memory stick that you carry with you. You can set the drive letter of the USB memory stick as a default keyfile search path. To do so, selectSettings -> Default Keyfiles. Then click
Add Path, browse to the drive letter assigned to the USB memory stick, and clickOK. Now each time you mount a volume (and if the optionUse keyfiles is checked in the password dialog window), VeraCrypt will scan the path and use all files that it finds on the USB memory stick as keyfiles.
WARNING: When you add a folder (as opposed to a file) to the list of keyfiles, only the path is remembered, not the filenames! This means e.g. that if you create a new file in the folder or if you copy an additional file to the folder, then all volumes that used keyfiles from the folder will be impossible to mount (until you remove the newly added file from the folder).

 

Empty Password & Keyfile

When a keyfile is used, the password may be empty, so the keyfile may become the only item necessary to mount the volume (which we do not recommend). If default keyfiles are set and enabled when mounting a volume, then before prompting for a password, VeraCrypt first automatically attempts to mount using an empty password plus default keyfiles (however, this does not apply to the 'Auto-Mount Devices' function). If you need to set Mount Options (e.g., mount as read-only, protect hidden volume etc.) for a volume being mounted this way, hold down the Control (Ctrl) key while clicking Mount (or select Mount with Options from theVolumes menu). This will open the Mount Options dialog.

 

Quick Selection

Keyfiles and keyfile search paths can be quickly selected in the following ways:
  • Right-click the Keyfiles button in the password entry dialog window and select one of the menu items.
  • Drag the corresponding file/folder icons to the keyfile dialog window or to the password entry dialog.

 

Volumes -> Add/Remove Keyfiles to/from Volume

This function allows you to re-encrypt a volume header with a header encryption key derived from any number of keyfiles (with or without a password), or no keyfiles at all. Thus, a volume which is possible to mount using only a password can be converted to a volume that require keyfiles (in addition to the password) in order to be possible to mount. Note that the volume header contains the master encryption key with which the volume is encrypted. Therefore, the data stored on the volume willnot be lost after you use this function.
This function can also be used to change/set volume keyfiles (i.e., to remove some or all keyfiles, and to apply new ones).
Remark: This function is internally equal to the Password Change function.

When VeraCrypt re-encrypts a volume header, the original volume header is first overwritten 256 times with random data to prevent adversaries from using techniques such as magnetic force microscopy or magnetic force scanning tunneling microscopy [17] to recover the overwritten header (however, see also the chapter Security Requirements and Precautions).

 

Volumes -> Remove All Keyfiles from Volume

This function allows you to re-encrypt a volume header with a header encryption key derived from a password and no keyfiles (so that it can be mounted using only a password, without any keyfiles). Note that the volume header contains the master encryption key with which the volume is encrypted. Therefore, the data stored on the volume willnot be lost after you use this function.
Remark: This function is internally equal to the Password Change function.

When VeraCrypt re-encrypts a volume header, the original volume header is first overwritten 256 times with random data to prevent adversaries from using techniques such as magnetic force microscopy or magnetic force scanning tunneling microscopy [17] to recover the overwritten header (however, see also the chapter Security Requirements and Precautions).

 

Tools > Keyfile Generator

You can use this function to generate a file with random content, which you can use as a keyfile (recommended). This function uses the VeraCrypt Random Number Generator. Note that the resulting file size is always 64 bytes (i.e., 512 bits), which is also the maximum possible VeraCrypt password length.

 

Settings -> Default Keyfiles

Use this function to set default keyfiles and/or default keyfile search paths. This function is particularly useful if you, for example, store keyfiles on a USB memory stick that you carry with you. You can add its drive letter to the default keyfile configuration. To do so, click Add Path, browse to the drive letter assigned to the USB memory stick, and clickOK. Now each time you mount a volume (and if Use keyfiles is checked in the password dialog), VeraCrypt will scan the path and use all files that it finds there as keyfiles.

WARNING: When you add a folder (as opposed to a file) to your default keyfile list, only the path is remembered, not the filenames! This means e.g. that if you create a new file in the folder or if you copy an additional file to the folder, then all volumes that used keyfiles from the folder will be impossible to mount (until you remove the newly added file from the folder).

IMPORTANT: Note that when you set default keyfiles and/or default keyfile search paths, the filenames and paths are saved unencrypted in the fileDefault Keyfiles.xml. For more information, please see the chapterVeraCrypt System Files & Application Data.

* Found at the time when you are mounting the volume, changing its password, or performing any other operation that involves re-encryption of the volume header.
** However, if you use an MP3 file as a keyfile, you must ensure that no program modifies the ID3 tags within the MP3 file (e.g. song title, name of artist, etc.). Otherwise, it will be impossible to mount volumes that use the keyfile.

↧

Commented Unassigned: Favorites - remember TrueCrypt compatibility option [108]

March 7, 2015, 7:14 am
$
0
0
Hi, please remember TrueCrypt compatibility option when I add mounted volume to Favorites.
Comments: Hi, The TrueCrypt mode is part of the key derivation information (alongside the hash) and as such it is considered to be sensitive because it gives more information to any potentiel attacked. The design of VeraCrypt (as it was in TrueCrypt) tries to minimize the information leaks from its use and that's why the PRF (hash) and the TrueCrypt mode are not saved in the favorites information. For these reasons, this feature will not be implement.
↧

New Post: Is there a way to make VeraCrypt work on the Raspberry Pi?

March 7, 2015, 7:41 am
$
0
0
Merci Wared for writing the howto.

My only remark is that if would be better to add a step in the howto so that the users check that the source package has not been modified (for example by someone you may hack WordPress on the server). For that, you can put the PGP signature file at the same location and tell the users to download it alongside VeraCrypt official public key (either from https://www.idrix.fr/VeraCrypt/VeraCrypt_PGP_public_key.asc or any trusted public key repository using ID=0x54DDD393) and then check the signature of the source package using this key.

These are extra steps but they are important for such security software and it is better to protect against any future server compromise.

I will also add your howto to the contributed resources section (https://veracrypt.codeplex.com/wikipage?title=Contributed%20Resources) although I prefer to wait to have your feedback on my proposed modification.
↧
Search

Updated Wiki: Creating New Volumes

March 7, 2015, 1:31 pm
$
0
0

Creating a New VeraCrypt Volume

To create a new VeraCrypt file-hosted volume or to encrypt a partition/device (requires administrator privileges), click on ‘Create Volume’ in the main program window. VeraCrypt Volume Creation Wizard should appear. As soon as the Wizard appears, it starts collecting data that will be used in generating the master key, secondary key (XTS mode), and salt, for the new volume. The collected data, which should be as random as possible, include your mouse movements, key presses, and other values obtained from the system (for more information, please see the section Random Number Generator). The Wizard provides help and information necessary to successfully create a new VeraCrypt volume. However, several items deserve further explanation:

Hash Algorithm

Allows you to select which hash algorithm VeraCrypt will use. The selected hash algorithm is used by the random number generator (as a pseudorandom mixing function), which generates the master key, secondary key (XTS mode), and salt (for more information, please see the section Random Number Generator). It is also used in deriving the new volume header key and secondary header key (see the sectionHeader Key Derivation, Salt, and Iteration Count).

For information about the implemented hash algorithms, see the chapter Hash Algorithms.

Note that the output of a hash function is never used directly as an encryption key. For more information, please refer to the chapterTechnical Details.

Encryption Algorithm

This allows you to select the encryption algorithm with which your new volume will be encrypted. Note that the encryption algorithm cannot be changed after the volume is created. For more information, please see the chapterEncryption Algorithms.

Quick Format

If unchecked, each sector of the new volume will be formatted. This means that the new volume will beentirely filled with random data. Quick format is much faster but may be less secure because until the whole volume has been filled with files, it may be possible to tell how much data it contains (if the space was not filled with random data beforehand). If you are not sure whether to enable or disable Quick Format, we recommend that you leave this option unchecked. Note that Quick Format can only be enabled when encrypting partitions/devices.

Important: When encrypting a partition/device within which you intend to create a hidden volume afterwards, leave this option unchecked.

Dynamic

Dynamic VeraCrypt container is a pre-allocated NTFS sparse file whose physical size (actual disk space used) grows as new data is added to it. Note that the physical size of the container (actual disk space that the container uses) will not decrease when files are deleted on the VeraCrypt volume. The physical size of the container can onlyincrease up to the maximum value that is specified by the user during the volume creation process. After the maximum specified size is reached, the physical size of the container will remain constant.

Note that sparse files can only be created in the NTFS file system. If you are creating a container in the FAT file system, the optionDynamic will be disabled (“grayed out”).

Note that the size of a dynamic (sparse-file-hosted) VeraCrypt volume reported by Windows and by VeraCrypt will always be equal to its maximum size (which you specify when creating the volume). To find out current physical size of the container (actual disk space it uses), right-click the container file (in a Windows Explorer window, not in VeraCrypt), then selectProperties and see the Size on disk value.

WARNING: Performance of dynamic (sparse-file-hosted) VeraCrypt volumes is significantly worse than performance of regular volumes. Dynamic (sparse-file-hosted) VeraCrypt volumes are also less secure, because it is possible to tell which volume sectors are unused. Furthermore, if data is written to a dynamic volume when there is not enough free space in its host file system, the encrypted file system may get corrupted.

Cluster Size

Cluster is an allocation unit. For example, one cluster is allocated on a FAT file system for a one- byte file. When the file grows beyond the cluster boundary, another cluster is allocated. Theoretically, this means that the bigger the cluster size, the more disk space is wasted; however, the better the performance. If you do not know which value to use, use the default.

VeraCrypt Volumes on CDs and DVDs

If you want a VeraCrypt volume to be stored on a CD or a DVD, first create a file-hosted VeraCrypt container on a hard drive and then burn it onto a CD/DVD using any CD/DVD burning software (or, under Windows XP or later, using the CD burning tool provided with the operating system). Remember that if you need to mount a VeraCrypt volume that is stored on a read-only medium (such as a CD/DVD) under Windows 2000, you must format the VeraCrypt volume as FAT. The reason is that Windows 2000 cannot mount NTFS file system on read-only media (Windows XP and later versions of Windows can).

Hardware/Software RAID, Windows Dynamic Volumes

VeraCrypt supports hardware/software RAID as well as Windows dynamic volumes.

Windows Vista or later: Dynamic volumes are displayed in the ‘Select Device’ dialog window as \Device\HarddiskVolumeN.

Windows XP/2000/2003: If you intend to format a Windows dynamic volume as a VeraCrypt volume, keep in mind that after you create the Windows dynamic volume (using the Windows Disk Management tool), you must restart the operating system in order for the volume to be available/displayed in the ‘Select Device’ dialog window of the VeraCrypt Volume Creation Wizard. Also note that, in the ‘Select Device’ dialog window, a Windows dynamic volume is not displayed as a single device (item). Instead, all volumes that the Windows dynamic volume consists of are displayed and you can select any of them in order to format the entire Windows dynamic volume.

Additional Notes on Volume Creation

After you click the ‘Format’ button in the Volume Creation Wizard window (the last step), there will be a short delay while your system is being polled for additional random data. Afterwards, the master key, header key, secondary key (XTS mode), and salt, for the new volume will be generated, and the master key and header key contents will be displayed.

For extra security, the portions of the randomness pool, master key, and header key can be prevented from being displayed by unchecking the checkbox in the upper right corner of the corresponding field:



Note that only the first 128 bits of the pool/keys are displayed (not the entire contents).

You can create FAT (whether it will be FAT12, FAT16, or FAT32, is automatically determined from the number of clusters) or NTFS volumes (however, NTFS volumes can only be created by users with administrator privileges). Mounted VeraCrypt volumes can be reformatted as FAT12, FAT16, FAT32, or NTFS anytime. They behave as standard disk devices so you can right-click the drive letter of the mounted VeraCrypt volume (for example in the ‘Computer’ or ‘My Computer’ list) and select‘Format’.

For more information about creating VeraCrypt volumes, see also the section Hidden Volume.

 

Next Section >>

↧
↧

Updated Wiki: VeraCrypt System Files

March 7, 2015, 1:49 pm
$
0
0

VeraCrypt System Files & Application Data

Note: %windir% is the main Windows installation path (e.g., C:\WINDOWS)

VeraCrypt Driver

%windir%\SYSTEM32\DRIVERS\veracrypt.sys

Note: This file is not present when VeraCrypt is run in portable mode.

VeraCrypt Settings, Application Data, and Other System Files

WARNING: Note that VeraCrypt does not encrypt any of the files listed in this section (unless it encrypts the system partition/drive).

The following files are saved in the folder %APPDATA%\VeraCrypt\. In portable mode, these files are saved to the folder from which you run the file VeraCrypt.exe (i.e., the folder in which VeraCrypt.exe resides):

  • "Configuration.xml" (the main configuration file).
  • "System Encryption.xml" (temporary configuration file used during the initial process of in-place encryption/decryption of the system partition/drive).
  • "Default Keyfiles.xml"
    • Note: This file may be absent if the corresponding VeraCrypt feature is not used.
  • "Favorite Volumes.xml"
    • Note: This file may be absent if the corresponding VeraCrypt feature is not used.
  • "History.xml" (the list of last twenty files/devices attempted to be mounted as VeraCrypt volumes or attempted to be used as hosts for VeraCrypt volumes; this feature can be disabled – for more information, see the sectionNever Save History)
    • Note: This file may be absent if the corresponding VeraCrypt feature is not used.
  • "In-Place Encryption" (temporary configuration file used during the initial process of in-place encryption/decryption of a non-system volume).
  • "In-Place Encryption Wipe Algo" (temporary configuration file used during the initial process of in-place encryption/decryption of a non-system volume).
  • "Post-Install Task - Tutorial" (temporary configuration file used during the process of installation or upgrade of VeraCrypt).
  • "Post-Install Task - Release Notes" (temporary configuration file used during the process of installation or upgrade of VeraCrypt).

The following files are saved in the folder %ALLUSERSPROFILE%\VeraCrypt\:

  • "Original System Loader" (a backup of the original content of the first drive track made before the VeraCrypt Boot Loader was written to it).
    • Note: This file is absent if the system partition/drive has not been encrypted.

The following files are saved in the folder %windir%\system32 (32-bit systems) or %windir%\SysWOW64 (64-bit systems):

  • "VeraCrypt System Favorite Volumes.xml"
    • Note: This file may be absent if the corresponding VeraCrypt feature is not used.
  • VeraCrypt.exe
    • Note: A copy of this file is located in this folder only when mounting of system favorite volumes is enabled.

 

↧

New Post: RPM packages for Fedora/RedHat

March 8, 2015, 8:42 am
↧

New Post: Is there a way to make VeraCrypt work on the Raspberry Pi?

March 8, 2015, 10:21 am
$
0
0
Thank you for you help !

I have updated the howto.

Wared
↧

Commented Unassigned: Maximum volume size in xp-32 [104]

March 8, 2015, 10:58 am
$
0
0
Good day, thank you for your work on the truecrypt successor!

I have a problem, here is a detailed description:

The 4TB file-based volume is on a 4TB usb3 hdd. Both the hdd and volume use 4kb blocks (that might be the problem).
It can be mounted on linux and win7-64.

When I try to mount it on xp-32-sp3 then the "please wait..." dialog appears for a few seconds but when it closes itself veracrypt's drive-list shows nothing has been mounted (same in windows explorer). (The xp-32-sp3 can mount an 8gb file-based volume on an 8gb stick.)
I tried both "VeraCrypt Setup 1.0f-XP Fix.exe" and the regular one (the ..fix.exe both as portable and installed).

Windows Event log shows this (translation below):

Ereignistyp: Informationen
Ereignisquelle: Service Control Manager
Ereigniskategorie: Keine
Ereigniskennung: 7035
Datum: 05.03.2015
Zeit: 09:53:28
Benutzer: D\a
Computer: D
Beschreibung:
Der Steuerbefehl "starten" wurde erfolgreich an den Dienst "veracrypt" gesendet.

translation: the command "start" has been successfully sent to the Service "veracrypt".

How large is too large for a veracrypt volume that has to be mounted on a xp-32 box? (And is it documented already?)
Do you want to fix this and if so then how can I help (I know c++ but not your codebase)?


Comments: I used the drive letter of the mounted volume ie "the inside" (not the letter of the drive the image-file is on). You are still welcome to log into the machine using Teamviewer. Or maybe you want to try it on your machine using an xp-32-pro in VirtualBox?
↧
↧

New Post: bootloader multilanguage

March 8, 2015, 11:49 am
$
0
0
There has already been discussion of having VeraCrypt incorporate a Linux-type mini-OS in the bootloader which is capable of implementing all keyboard layouts. This will obviously be a feature considered very desirable by non-Western users, and I anticipate that demand for this feature will be very strong in the future as VeraCrypt gains international popularity,

Issue to rewrite the bootloader as 32-bit code here: https://veracrypt.codeplex.com/workitem/27

Issue to rewrite the bootloader as 64-bit code here: https://veracrypt.codeplex.com/workitem/72

Question for Mounir: would the Linux-type mini-OS bootloader become possible under 32-bit, or is 64-bit necessary for that?
↧

Commented Unassigned: file container timestamp on Mint Xfce [105]

March 8, 2015, 12:55 pm
$
0
0

Hi,

This is about the timestamp of file containers for backups and dropbox use.

I read:
http://stackoverflow.com/questions/25877910/svn-veracrypt-dropbox


But I am unable to get the timestamp to change. I do the following test:

Linux Mint 17.1 Xfce edition
Veracrypt 1.0f-1, Jan 5

Options:
"preserve modification timestamp of file containers" is unchecked
mount options: -o flush,sync
"do not use kernel cryptographic services" is checked
"do not accelerate AES encryption/decryption by using the AES instractions of the processor" is checked

create 1 Mb FAT file container test.tc on local SSD in Dropbox folder
ls -al test.tc shows time 11:09
start Veracrypt, mount, add a folder and a file with a few bytes
ls -al test.tc shows time 11:12
start Veracrypt, unmount
ls -al test.tc shows time 11:09

Am I missing something?

thanks,

Peter

Comments: I finally was able to reproduce the issue: it was due to the fact that when passing any argument to VeraCrypt command line (here file path), user preferences were not loaded unless the switch __--load-preferences__ is specified in the command line. So, you could solve your issue by adding this switch to the command line ("Exec=/usr/bin/veracrypt --load-preferences"). Nevertheless, I have implemented a fix in the code in order to load the preferences in cases we only pass the volume path as an argument: https://veracrypt.codeplex.com/SourceControl/changeset/efee53d07ad1464067d599e04f42f45af0e2836a I have built new Linux binaries for the 1.0f-2-Beta that contain this fix. You can download them from the Nightly Builds folder on Sourceforge: https://sourceforge.net/projects/veracrypt/files/VeraCrypt%20Nightly%20Builds/ Thank you for reporting this.
↧
Search

Edited Issue: file container timestamp on Mint Xfce [105]

March 8, 2015, 12:55 pm
$
0
0

Hi,

This is about the timestamp of file containers for backups and dropbox use.

I read:
http://stackoverflow.com/questions/25877910/svn-veracrypt-dropbox


But I am unable to get the timestamp to change. I do the following test:

Linux Mint 17.1 Xfce edition
Veracrypt 1.0f-1, Jan 5

Options:
"preserve modification timestamp of file containers" is unchecked
mount options: -o flush,sync
"do not use kernel cryptographic services" is checked
"do not accelerate AES encryption/decryption by using the AES instractions of the processor" is checked

create 1 Mb FAT file container test.tc on local SSD in Dropbox folder
ls -al test.tc shows time 11:09
start Veracrypt, mount, add a folder and a file with a few bytes
ls -al test.tc shows time 11:12
start Veracrypt, unmount
ls -al test.tc shows time 11:09

Am I missing something?

thanks,

Peter

↧

Updated Wiki: Home

March 8, 2015, 1:30 pm
$
0
0

Project Description

VeraCrypt is a free disk encryption software brought to you by IDRIX (https://www.idrix.fr) and that is based on TrueCrypt.

Donate to VeraCryptFaire un don à VeraCryptSpenden für VeraCrypt

VeraCrypt on FacebookVeraCrypt on Twitter

Frequently Asked Question

Online Documentation (click here for latest User Guide PDF)

Windows / MacOSX / Linux / Source Downloads

Android & iOS Support

Release Notes

Contributed Resources & Downloads (PPA, RPM, ARM, Raspberry Pi...)

 

What does VeraCrypt bring to you?

VeraCrypt adds enhanced security to the algorithms used for system and partitions encryption making it immune to new developments in brute-force attacks.
VeraCrypt 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 harder for an attacker to gain access to the encrypted data.

Starting from version 1.0f, VeraCrypt can load TrueCrypt volume. It also offers the possibility to convert TrueCrypt containers and non-system partitions to VeraCrypt format.

UPDATE January 5th 2015 : Support of the old TrueCrypt 6.0 has been included inVeraCrypt 1.0f-1, which is a minor update of VeraCrypt 1.0f.

UPDATE December 30th 2014 : VeraCrypt 1.0f is out with many new features and enhancements. The most notable ones are the support of mounting and converting TrueCrypt volumes, and the speedup of the mounting process through the manual selection of the correct PRF algorithm. Download for Windows is here.

As usual, a MacOSX version is available in the Downloads section or by clicking on the following link. It supports MacOSX 10.6 and above and it requires OSXFUSE 2.3 and later(https://osxfuse.github.io/).MacFUSE compatibility layer must checked during OSXFUSE installation.
Also a Linux version is available in the Downloads section or by clicking on the following link. The package contains the installation scripts for 32-bit and 64-bit versions, and for GUI and console-only version (choose which script is adapted the best to your machine).

All released files are signed with a PGP key available on the following link :https://www.idrix.fr/VeraCrypt/VeraCrypt_PGP_public_key.asc . It's also available on major key servers with ID=0x54DDD393.
Please check that its fingerprint is 993B7D7E8E413809828F0F29EB559C7C54DDD393.

SHA256 and SHA512 sums for all released files are available in the Downloads section.

VeraCrypt on the fly encrypting the system partition :
VeraCrypt Partition Encryption


VeraCrypt creating an encrypted volume :

VeraCrypt encrypted volume creation

Changing the GUI language of VeraCrypt
VeraCrypt Language Selection Dialog

↧
↧

Closed Unassigned: Favorites - remember TrueCrypt compatibility option [108]

March 8, 2015, 1:43 pm
$
0
0
Hi, please remember TrueCrypt compatibility option when I add mounted volume to Favorites.
↧

Updated Wiki: Contributed Resources

March 8, 2015, 1:49 pm
$
0
0

Here you'll find useful resources contributed by VeraCrypt users.

Third party binaries:

Tutorials:

Miscellaneous:

  • vcsteg2.py : a Python script that tries to hide a VeraCrypt volume inside a video file (Steganography)
↧

Updated Wiki: Contributed Resources

March 8, 2015, 1:52 pm
$
0
0

Here you'll find useful resources contributed by VeraCrypt users.

Third party binaries:

Tutorials:

Miscellaneous:

  • vcsteg2.py : a Python script that tries to hide a VeraCrypt volume inside a video file (Steganography)
↧
Viewing all 7620 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>