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

Created Unassigned: VeraCrypt changes password over two hours [239]

$
0
0

I decided to convert disk-based non-system TrueCrypt volume to VeraCrypt format. I entered correctly all parameters for TrueCrypt volume and selected parameters for resulting VeraCrypt volume. PIM I selected was non-default, but for sure in reasonable range - i checked correct value entry using "Show password" option.
Wipe passes were selected to be 256.

Operation started over two hours ago and it continues to this moment. I checked VeraCrypt.exe process using Sysinternals Process Explorer - it produces continuous CPU load of 12,50%, it makes some constant I/O activity in very small (30 kilobytes) and slow increments. Besides that, the progress bar is active but there is still no end of this operation.

I have run the same operation on other disk-based volume, where the only major difference of settings was parameter of wipe passes, which I have set to 1. The whole conversion finished in less than two minutes.

My question is: should I wait for this stuck process to finish, or do I need to assume that something wrong happened?



New Post: Veracrypt mounting same volume under 2 drives letters

$
0
0
Idrassi's method seems to have worked for me. Thank you

Commented Unassigned: VeraCrypt mounts container on two letters (drives) / Windows [238]

$
0
0
I'am trying to switch from TrueCrypt to VeraCrypt, but I have got some weird problem.

I have just created test container and when I try to mount it, for some reason VeraCrypt mounts container on two drives. (like I mount on Z and got it too on D or I mount on W and also got it on G). And they both accessible.

Also it leaves "ghost" drives after that.

I thought it was some truecrypt and veracrypt conflict at first, I have tried to remove them both, reboot, install VeraCrypt again, but the same problem still exists.

Video: https://www.youtube.com/watch?v=r7mNpP6pG9A

Comments: Idrassi's method under Discussion 645527 seems to have worked for me

Edited Unassigned: VeraCrypt changes password over two hours [239]

$
0
0

I decided to convert disk-based non-system TrueCrypt volume to VeraCrypt format. I entered correctly all parameters for TrueCrypt volume and selected parameters for resulting VeraCrypt volume. PIM I selected was non-default, but for sure in reasonable range - i checked correct value entry using "Show password" option.
Wipe passes were selected to be 256.

Operation started over two hours ago and it continues to this moment. I checked VeraCrypt.exe process using Sysinternals Process Explorer - it produces continuous CPU load of 12,50%, it makes some constant I/O activity in very small (30 kilobytes) and slow increments. Besides that, the progress bar is active but there is still no end of this operation.

I have run the same operation on other disk-based volume, where the only major difference of settings was parameter of wipe passes, which I have set to 1. The whole conversion finished in less than two minutes.

My question is: should I wait for this stuck process to finish, or do I need to assume that something wrong happened?


Commented Unassigned: VeraCrypt changes password over two hours [239]

$
0
0

I decided to convert disk-based non-system TrueCrypt volume to VeraCrypt format. I entered correctly all parameters for TrueCrypt volume and selected parameters for resulting VeraCrypt volume. PIM I selected was non-default, but for sure in reasonable range - i checked correct value entry using "Show password" option.
Wipe passes were selected to be 256.

Operation started over two hours ago and it continues to this moment. I checked VeraCrypt.exe process using Sysinternals Process Explorer - it produces continuous CPU load of 12,50%, it makes some constant I/O activity in very small (30 kilobytes) and slow increments. Besides that, the progress bar is active but there is still no end of this operation.

I have run the same operation on other disk-based volume, where the only major difference of settings was parameter of wipe passes, which I have set to 1. The whole conversion finished in less than two minutes.

My question is: should I wait for this stuck process to finish, or do I need to assume that something wrong happened?


Comments: And the answer is: do not use 256 passes option until you really want to wait really long. Process completed and encrypted partition is accesible without problems.

Commented Unassigned: VeraCrypt mounts container on two letters (drives) / Windows [238]

$
0
0
I'am trying to switch from TrueCrypt to VeraCrypt, but I have got some weird problem.

I have just created test container and when I try to mount it, for some reason VeraCrypt mounts container on two drives. (like I mount on Z and got it too on D or I mount on W and also got it on G). And they both accessible.

Also it leaves "ghost" drives after that.

I thought it was some truecrypt and veracrypt conflict at first, I have tried to remove them both, reboot, install VeraCrypt again, but the same problem still exists.

Video: https://www.youtube.com/watch?v=r7mNpP6pG9A

Comments: Unfortunately I have now found that Idrassi's method has not worked; it just took a while for the ghosts to reappear

Commented Unassigned: VeraCrypt mounts container on two letters (drives) / Windows [238]

$
0
0
I'am trying to switch from TrueCrypt to VeraCrypt, but I have got some weird problem.

I have just created test container and when I try to mount it, for some reason VeraCrypt mounts container on two drives. (like I mount on Z and got it too on D or I mount on W and also got it on G). And they both accessible.

Also it leaves "ghost" drives after that.

I thought it was some truecrypt and veracrypt conflict at first, I have tried to remove them both, reboot, install VeraCrypt again, but the same problem still exists.

Video: https://www.youtube.com/watch?v=r7mNpP6pG9A

Comments: I used Windows 8, it showed the same problems. Mounting the same drive automatically to two drive letters, and three ghost drive letters showed up and never disappear.

Commented Unassigned: "Veracrypt::SecurityToken::Initlibrary:523" error [224]

$
0
0
Hey all!
I am using my Mac Leopard with Veracrypt last version and I get the cryptic message "No such file or directory" and "Veracrypt::SecurityToken::Initlibrary:523".
I tried to desinstall Veracrypt, MacFuse and so one --> no result
Reinstallation does not help.
The windows does actually not close when I press on okay.
Does anybody have any Idea? I would try to suppress any initialization file but I can find any of them. Any help welcome :-)
Have a nice week-end! Alex
Comments: Hi Alex, You seem to use a PKCS#11 module to access your keyfile on a smart card. Do you confirm? This error indicates that VeraCrypt was not able to load the PKCS#11 library you specified on the preferences. Either remove the PKCS#11 library from VeraCrypt preferences or check that the library still exists and that it is loaded (for example by testing it on Firefox).

Commented Unassigned: Volumes are mounted twice [226]

$
0
0
I'd like to mount VeraCrypt volumes using the command line like this:

```
%ProgramW6432%\VeraCrypt\VeraCrypt.exe /quit /cache yes /mountoption removable /volume \Device\Harddisk0\Partition0 /letter Z
```

The drive letter `Z` is then mounted as a removable device, but other another drive letter (the first that's available) is mounted as well.

The previously unassigned drive letter stays visible in Windows/File Explorer until the computer is rebooted (see attachment).

I'm using Windows 10 Pro.
Comments: Thanks to all and especially Leon for the detailed analysis. The fix for the TrueCrypt has side effects which are difficult to avoid at this stage. I'm working on a better fix but it proves very challenging. As I have written for the recycle bin issue (https://veracrypt.codeplex.com/discussions/645558#post1446829) there is a risk that it will not be possible to solve the TrueCrypt vulnerability without introducing instabilities like these ones. Of course, it is out of question to leave this vulnerability open for exploits so the priority now is to come up with technical solutions that may even requires a big change in the internal architecture. I'll keep you informed.

New Post: Veracrypt mounting same volume under 2 drives letters

$
0
0
Thanks to all for your comments and feedback.

The fix for the TrueCrypt vulnerability brings stability issues which are difficult to avoid at this stage. I'm working on a better fix but it proves very challenging. As I have written for the recycle bin issue (https://veracrypt.codeplex.com/discussions/645558#post1446829) there is a risk that it will not be possible to solve the TrueCrypt vulnerability without introducing instabilities like these ones.

Of course, it is out of question to leave this vulnerability open for exploits so the priority now is to come up with technical solutions that may even require a big change in the internal architecture.

I'll keep you informed.

Commented Unassigned: "Veracrypt::SecurityToken::Initlibrary:523" error [224]

$
0
0
Hey all!
I am using my Mac Leopard with Veracrypt last version and I get the cryptic message "No such file or directory" and "Veracrypt::SecurityToken::Initlibrary:523".
I tried to desinstall Veracrypt, MacFuse and so one --> no result
Reinstallation does not help.
The windows does actually not close when I press on okay.
Does anybody have any Idea? I would try to suppress any initialization file but I can find any of them. Any help welcome :-)
Have a nice week-end! Alex
Comments: Hi! Thank you for your answer. This is exactly what I try to do. The point is that I cannot access to the parameter window of Veracrypt, as the windows with the error message is again and again popping up. I would do it in a command line, but I don´t know where to look for the files! Best regards, Alexandre Mantion

Commented Unassigned: VeraCrypt mounts container on two letters (drives) / Windows [238]

$
0
0
I'am trying to switch from TrueCrypt to VeraCrypt, but I have got some weird problem.

I have just created test container and when I try to mount it, for some reason VeraCrypt mounts container on two drives. (like I mount on Z and got it too on D or I mount on W and also got it on G). And they both accessible.

Also it leaves "ghost" drives after that.

I thought it was some truecrypt and veracrypt conflict at first, I have tried to remove them both, reboot, install VeraCrypt again, but the same problem still exists.

Video: https://www.youtube.com/watch?v=r7mNpP6pG9A

Comments: i have the same problem in windows 7. i copied a truecrypt containerfile, activated truecrypt in the menu,changed the password in veracrypt, mounted the containerfile, i could access in totalcommander the containerfile via 2 driveletters, only one driveletter showed up in the veracrypt menu, after dismounting the driveletter appearing in the Veracryptmenu tthe 2 driveletters became inaccessible in Totalcommander, but were still there, even after closing totalcommander and restarting totalcommander. This is a serious bug, i can not convert my truecrypt devices to veracrypt devices as long as this problem is not solved icy007

New Post: VeraCrypt 1.15 Recycle Bin not working on VeraCrypt drive

$
0
0
anf this forbids many of the usual actions.
What else? Is Veracrypt still safe to use, especially in terms of data loss?

New Post: New Laptop and Windows 7 (downgrade from 8.1)

$
0
0
Hi All,

I have question about my new laptop and UEFI motherboard,
please tell me is it possible to install VeraCrypt and encrypt whole hard disk if
my my laptop have installed Windows 7 Pro on MBR drive with UEFI ?
(downgrade rights from Windows 8.1)

Thank you,Tulip91

Updated Wiki: Command Line Usage

$
0
0

Command Line Usage

Note that this section applies to the Windows version of VeraCrypt. For information on command line usage applying to theLinux and Mac OS X versions, please run: veracrypt –h

/help or /?Display command line help.
/truecrypt or /tcActivate TrueCrypt compatibility mode which enables mounting volumes created with TrueCrypt 6.x and 7.x series.
/hashIt must be followed by a parameter indicating the PRF hash algorithm to use when mounting the volume. Possible values for /hash parameter are: sha256, sha-256, sha512, sha-512, whirlpool, ripemd160 and ripemd-160. When /hash is omitted, VeraCrypt will try all possible PRF algorithms thus lengthening the mount operation time.
/volume or /vIt must be followed by a parameter indicating the file and path name of a VeraCrypt volume to mount (do not use when dismounting). To mount a partition/device-hosted volume, use, for example,

/v \Device\Harddisk1\Partition3 (to determine the path to a partition/device, run VeraCrypt and clickSelect Device). You can also mount a partition or dynamic volume using its volume name (for example,

/v \\?\Volume{5cceb196-48bf-46ab-ad00-70965512253a}\). To determine the volume name use e.g. mountvol.exe. Also note that device paths are case-sensitive.

/letter or /lIt must be followed by a parameter indicating the driver letter to mount the volume as. When /l is omitted and when /a is used, the first free drive letter is used.
/explore or /eOpen an Explorer window after a volume has been mounted.
/beep or /bBeep after a volume has been successfully mounted or dismounted.
/auto or /aIf no parameter is specified, automatically mount the volume. If devices is specified as the parameter (e.g., /a devices), auto-mount all currently accessible device/partition-hosted VeraCrypt volumes. If favorites is specified as the parameter, auto-mount favorite volumes. Note that /auto is implicit if /quit and /volume are specified. If you need to prevent the application window from appearing, use /quit.
/dismount or /dDismount volume specified by drive letter (e.g., /d x). When no drive letter is specified, dismounts all currently mounted VeraCrypt volumes.
/force or /fForces dismount (if the volume to be dismounted contains files being used by the system or an application) and forces mounting in shared mode (i.e., without exclusive access).
/keyfile or /kIt must be followed by a parameter specifying a keyfile or a keyfile search path. For multiple keyfiles, specify e.g.: /k c:\keyfile1.dat /k d:\KeyfileFolder /k c:\kf2 To specify a keyfile stored on a security token or smart card, use the following syntax: token://slot/SLOT_NUMBER/file/FILE_NAME
/tokenlibIt must be followed by a parameter indicating the PKCS #11 library to use for security tokens and smart cards. (e.g.: /tokenlib c:\pkcs11lib.dll)
/cache or /cIf it is followed by y or yes or if no parameter is specified: enable password cache;
if it is followed by n or no: disable password cache (e.g., /c n).
if it is followed by f or favorites: temporary cache password when mounting multiple favorites  (e.g., /c f).
Note that turning the password cache off will not clear it (use /w to clear the password cache).
/history or /hif it is followed by y or no parameter: enables saving history of mounted volumes; if it is followed byn: disables saving history of mounted volumes (e.g., /h n).
/wipecache or /wWipes any passwords cached in the driver memory.
/password or /pIt must be followed by a parameter indicating the volume password. If the password contains spaces, it must be enclosed in quotation marks (e.g., /p ”My Password”). Use /p ”” to specify an empty password.Warning: This method of entering a volume password may be insecure, for example, when an unencrypted command prompt history log is being saved to unencrypted disk.
/pimIt must be followed by a positive integer indicating the PIM (Personal Iterations Multiplier) to use for the volume.
/quit or /qAutomatically perform requested actions and exit (main VeraCrypt window will not be displayed). If preferences is specified as the parameter (e.g., /q preferences), then program settings are loaded/saved and they override settings specified on the command line. /q background launches the VeraCrypt Background Task (tray icon) unless it is disabled in the Preferences.
/silent or /sIf /q is specified, suppresses interaction with the user (prompts, error messages, warnings, etc.). If /q is not specified, this option has no effect.
/mountoption or /m

It must be followed by a parameter which can have one of the values indicated below.

ro or readonly: Mount volume as read-only.

rm or removable: Mount volume as removable medium (see sectionVolume Mounted as Removable Medium).

ts or timestamp: Do not preserve container modification timestamp.

sm or system: Without pre-boot authentication, mount a partition that is within the key scope of system encryption (for example, a partition located on the encrypted system drive of another operating system that is not running). Useful e.g. for backup or repair operations. Note: If you supply a password as a parameter of /p, make sure that the password has been typed using the standard US keyboard layout (in contrast, the GUI ensures this automatically). This is required due to the fact that the password needs to be typed in the pre-boot environment (before Windows starts) where non-US Windows keyboard layouts are not available.

bk or headerbak: Mount volume using embedded backup header. Note: All volumes created by VeraCrypt contain an embedded backup header (located at the end of the volume).

recovery: Do not verify any checksums stored in the volume header. This option should be used only when the volume header is damaged and the volume cannot be mounted even with the mount option headerbak. Example: /m ro.

label=LabelValue: Use the given string value LabelValue as a label of the mounted volume in Windows Explorer. The maximum length forLabelValue  is 32 characters for NTFS volumes and 11 characters for FAT volumes. For example,/m label=MyDrive will set the label of the drive in Explorer to MyDrive.

Please not that this switch may be present several times in the command line in order to specify multiple mount options (e.g.: /m rm /m ts)

VeraCrypt Format.exe (VeraCrypt Volume Creation Wizard):

/createCreate a container based volume in command line mode. It must be followed by the file name of the container to be created.
/size

(Only with /create)
It must be followed by a parameter indicating the size of the container file that will be created. This parameter is a number indicating the size in Bytes. It can have a suffixe 'K', 'M', 'G' or 'T' to indicate that the value is in Kilobytes, Megabytes, Gigabytes or Terabytes respectively. For example:

  • /size 5000000: the container size will be 5000000 bytes
  • /size 25K: the container size will be 25 KiloBytes.
  • /size 100M: the container size will be 100 MegaBytes.
  • /size 2G: the container size will be 2 GigaBytes.
  • /size 1T: the container size will be 1 TeraBytes.
 /password (Only with /create)
It must be followed by a parameter indicating the password of the container that will be created.
 /hash(Only with /create)
It must be followed by a parameter indicating the PRF hash algorithm to use when creating the volume. It has the same syntax as VeraCrypt.exe.
/encryption(Only with /create)
It must be followed by a parameter indicating the encryption algorithm to use. The default is AES if this switch is not specified. The parameter can have the following values (case insensitive):
  • AES
  • Serpent
  • Twofish
  • AES(Twofish)
  • AES(Twofish(Serpent))
  • Serpent(AES)
  • Serpent(Twofish(AES))
  • Twofish(Serpent)
/filesystem(Only with /create)
It must be followed by a parameter indicating the file system to use for the volume. The parameter can have the following values:
  • None: don't use any filesystem
  • FAT: format using FAT/FAT32
  • NTFS: format using NTFS. Please not that in this case a UAC prompt will be displayed unless the process is run with full administrative privileges.
/dynamic(Only with /create)
It has no parameters and it indicates that the volume will be created as a dynamic volume.
/force(Only with /create)
It has no parameters and it indicates that overwrite will be forced without requiring user confirmation.
/silent(Only with /create)
It has no parameters and it indicates that no message box or dialog will be displayed to the user. If there is any error, the operation will fail silently.
/noisocheck or /nDo not verify that VeraCrypt Rescue Disks are correctly burned. WARNING: Never attempt to use this option to facilitate the reuse of a previously created VeraCrypt Rescue Disk. Note that every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk even if you use the same password. A previously created VeraCrypt Rescue Disk cannot be reused as it was created for a different master key.

Syntax

VeraCrypt.exe [/tc] [/hash {sha256, sha-256, sha512, sha-512,whirlpool, ripemd160, ripemd-160}] [/a [devices|favorites]] [/b] [/c [y|n]] [/d [drive letter]] [/e] [/f] [/h [y|n]] [/k keyfile or search path] [/l drive letter] [/m {bk|rm|recovery|ro|sm|ts}] [/p password] [/q [background|preferences]] [/s] [/tokenlib path] [/v volume] [/w]

"VeraCrypt Format.exe" [/n] [/create] [/size number[{K, M, G, T}]] [/p password]  [/encryption {AES, Serpent, Twofish, AES(Twofish), AES(Twofish(Serpent)), Serpent(AES), Serpent(Twofish(AES)), Twofish(Serpent)}] [/hash {sha256, sha-256, sha512, sha-512,whirlpool, ripemd160, ripemd-160}]

[/hash {sha256, sha-256, sha512, sha-512,whirlpool, ripemd160, ripemd-160}] [/filesystem {None, FAT, NTFS}] [/dynamic] [/force] [/silent]

Note that the order in which options are specified does not matter.

Examples

Mount the volume d:\myvolume as the first free drive letter, using the password prompt (the main program window will not be displayed):

veracrypt /q /v d:\myvolume

Dismount a volume mounted as the drive letter X (the main program window will not be displayed):

veracrypt /q /d x

Mount a volume called myvolume.tc using the password MyPassword, as the drive letterX. VeraCrypt will open an explorer window and beep; mounting will be automatic:

veracrypt /v myvolume.tc /l x /a /p MyPassword /e /b

Create a 10 MB file container using the password test and formatted using FAT:

"C:\Program Files\VeraCrypt\VeraCrypt Format.exe" /create c:\Data\test.hc /password test /hash sha512 /encryption serpent /filesystem FAT /size 10M /force


Commented Unassigned: Expand Raid5 "successful" [228]

$
0
0
Hi,

i have expanded my partition encryption from ~10tb to 16,7tb (16753,17GB) (Raid 5). My filesystem is NTFS. The last expand worked gread but this time the tool says successful and I can mount the volume, BUT windows only give me the option to format it, because no filesystem is found on the mounted volume. Is there any possibility to get my data back (i have no header backups) ??
Comments: -> can be closed, this issue has nothing to do with veracrypt NTFS with default 4096 Bytes clusters only supports 17.592.186.040.320Bytes -> ~16TB Windows can't read the partition after expand to more then 16tb, but it is possible to mount the volume on linux...

New Post: VeraCrypt 1.15 Recycle Bin not working on VeraCrypt drive

$
0
0
On another note: I'm guessing with all these updates regarding security, password headers need to be updated for the benefits?
And to bump Arne001's question, is it safe to stay with v1.13 to prevent data lost of a corrupted Recycle bin?
I have not updated from 1.13 yet, I'm afraid to.

Keep up the good work idrassi, As always, your efforts are more appreciated then we can put into words!

Commented Issue: Veracrypt Looks weird in Launchpad (OSX) [48]

$
0
0
(Priority extra low)

See attached.

Veracrypt looks like it's been passed through a gaussian blur in launchpad in OSX and it's the only application that seems to do this.
Comments: I created a higher resolution icon for VeraCrypt. You can replace the existing icon with this one manually. http://www.visualpharm.com/articles/change_mac_icons.html

Commented Unassigned: Volumes are mounted twice [226]

$
0
0
I'd like to mount VeraCrypt volumes using the command line like this:

```
%ProgramW6432%\VeraCrypt\VeraCrypt.exe /quit /cache yes /mountoption removable /volume \Device\Harddisk0\Partition0 /letter Z
```

The drive letter `Z` is then mounted as a removable device, but other another drive letter (the first that's available) is mounted as well.

The previously unassigned drive letter stays visible in Windows/File Explorer until the computer is rebooted (see attachment).

I'm using Windows 10 Pro.
Comments: The fix tip offered by kannix (Sep 29 5:50pm) has also worked for me to permanently keep the unwanted second drive from being mounted: 1. Open a cmd window as administrator and for __each__ unwanted second drive mounted, execute the following command where X: is the second unwanted drive mounted. mountvol X: /d For example, if you mounted a VeraCrypt volume as drive Z: but in addition to Z: a second drive G: was also mounted, the command would be: mountvol G: /d 2. Immediately reboot. After restarting, when you then remount your VeraCrypt volume(s), the second mount is longer created for that boot or any subsequent boots. At least that's my experience, which is the same as that for kannix. My OS is Windows 10.

New Post: VeraCrypt 1.15 Recycle Bin not working on VeraCrypt drive

$
0
0
I did read the VC 1.15 release notes about the elevation bug in TC/VC, however I could not figure out how the bug can be exploited by an attacker to compromise the security of VC/TC. Can someone explain in a more or less easy to understand language, what is this bug all about (as from Idrassi's comment it sounds quite an issue)?
thanks
Viewing all 7620 articles
Browse latest View live


Latest Images

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