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

New Post: I failed to change the date of the VeraCrypt file. But is this possible at all?

$
0
0
Sorry,

I tried to modify the date while the file was still mounted ... the dates can be changed.

New Post: 1.of-2 - Favorites requires multiple passwords

$
0
0
I upgraded to 1.of-2 and now it requires multiple passwords for favorites. I have two favorite volumes with the same password. Before when I mounted favorites I was prompted for the password one time and both volumes mounted. With 1.of-2 it now mounts the first volume and then I get a second password prompt. The end result is it takes much longer to mount the two volumes and it is more cumbersome. I removed all favorites and then recreated them but that didn't resolve it.

I was able to find a copy of 1.of-1 and re-install it and it again worked as expected. I'm OK for now but would like to move to the newer version when this gets fixed.

New Post: 1.of-2 - Favorites requires multiple passwords

$
0
0
Hello Steven,

Version 1.0f-2 removed the auto temporary caching of the password due to delays mounting volumes caused when you have two or more volumes with different passwords in the favorites having to exhaust the four password hashing algorithms before prompting for the next volume's password.

In the latest version, you can enable in the preferences the option "Temporary Cache password during Mount Favorite Volumes operations" to enable the auto temporary caching of the password for volumes in favorites.

Regards.

New Post: RPM packages for Fedora/RedHat

Created Unassigned: An assertion failed(!)/XTerm [121]

$
0
0
Hi.

I've just upgraded to the latest release from the previous build for Linux 64bit and whilst Veracrypt opens fine, I couldn't help but notice that this time around (installed via PPA on this occasion..) when installing in KDE (4), XTerm and UXTerm are installed also.. Listed as dependencies in fact. I was just wondering why that might be the case..

Additionally when I clicked on the 'About' under the 'Help' menu to ensure I had upgraded correctly, I receive the following assertion failed message as detailed in the attached.

Wondered whether you might be able to address either of these concerns..?

I am running Kubuntu 14.04 LTS 64bit incidentally if that helps.

Regards,

Chuck

New Post: 1.of-2 - Favorites requires multiple passwords

$
0
0
I still have the problem. It works when mounting favorites from within the VC UI but not from the command line. I have a script that launches two volumes and when complete launches a program. With 1.of-2 when using the script it re-prompts for the password after mounting the first volume.

It works as expected from the VeraCrypt interface.

New Post: 1.of-2 - Favorites requires multiple passwords

$
0
0
I was able to fix it in my script by adding /cache y and in another script the /wipecache tags.

Adding these script tags in addition to the settings Enigma2Illusion suggested seem to have things back to normal.

New Post: 1.of-2 - Favorites requires multiple passwords


New Post: System encrypt 2 hard drives

$
0
0
Oh Thanks a lot,
for any reasons i did not pay attention to the favorite volumes..
Keep on going with your programm, it's going to be more and more important for all of us.

Commented Unassigned: An assertion failed(!)/XTerm [121]

$
0
0
Hi.

I've just upgraded to the latest release from the previous build for Linux 64bit and whilst Veracrypt opens fine, I couldn't help but notice that this time around (installed via PPA on this occasion..) when installing in KDE (4), XTerm and UXTerm are installed also.. Listed as dependencies in fact. I was just wondering why that might be the case..

Additionally when I clicked on the 'About' under the 'Help' menu to ensure I had upgraded correctly, I receive the following assertion failed message as detailed in the attached.

Wondered whether you might be able to address either of these concerns..?

I am running Kubuntu 14.04 LTS 64bit incidentally if that helps.

Regards,

Chuck
Comments: Hi, I asked the PPA maintainer about the XTerm dependency and I'll update this ticket with his answer. My personal opinion is that it is a dependency of wxWidgets on Ubuntu since the PPA binaries are linked against the official Ubuntu wxWidgets library and replay the system tray icon with an application indicator applet. On the other hand, VeraCrypt official Linux binaries are linked against unmodified official wxWidgets sources with minimal dependencies in order to run on all Linux distributions. To avoid any conflicts and dependency issues, it is always advisable to use the official VeraCrypt binaries. Concerning the assertion failed message, this is a know issue with wxWidgets and code generated by wxFormBuilder: http://trac.wxwidgets.org/ticket/14594 The official VeraCrypt binaries are linked against a static wxWidgets library where this type of harmless assertions are not displayed. So, that's why there is no such message when using them. The PPA binaries are linked against Ubuntu wxWidgets library which is more verbose and that's why you get such messages. I didn't address this since it doesn't manifest itself with the official binaries. The obvious solution would be to make wxFormBuilder generate calls to SetMaxLength that doen't use 0 on GTK, but this needs some work. Another way would be to turn off wxWidgets assertion programatically but this is not clean. Anyway, I'll try to find the best solution for these assertions. For now, either ignore them or use the official VeraCrypt binary.

New Post: implementation of camellia algorithm

$
0
0
implementation of camellia cascade algorithm such

AES-SERPENT-TWOFISH-CAMELLIA

could even consider the option of implementing the algorithm GOST together

Created Unassigned: Decrypt System Drive/Partition on Another Machine [122]

$
0
0
Hello Mounir,

For tracking purposes, I am creating this ticket to allow decrypting the system drive/partition on another machine when the rescue disk is not available.

Referencing thread:

http://sourceforge.net/p/veracrypt/discussion/features/thread/55085a7a/

Thank you!

New Post: Cloud usage: Store a volume like a file by unencripted file

$
0
0
I know that encfs is not the safest way, this is the reason by I don't use it. But its design is interesting: Mount a common directory that contains a metadata file (equivalent to the first 65536 bytes of a tc volume) plus a encrypted file by each plain file.

The use a script + GPG is not the same, because isn't a encrypted volume. To open this files first must be unencrypt, and when you finish, encrypt again.

My suggestion is allow to store a veracrypt volume like a directory of files instead of a single file.

New Post: Mount 2 containers in 1 file batch

$
0
0
Hello :)

I have this file for load my 1st container :
VeraCrypt /tc /letterG /quit /volume "C:\Users\USER\Documents\CONTAINER"
I want to know if it's possible to load the 2nd container, if the 1st is mount, in PHP example :
<?php
if(mount(1_st_container))
{
     load(2_nd_container);
}

else
{
     load(1_st_container);
}
Do you know if it's possible in batch ?

Thanks

Created Unassigned: veracrypt from git will not compile on Manjaro [123]

$
0
0
When ever I try and compile veracrypt from the github version I get the following error message:

Compiling WizardFrame.cpp
Linking veracrypt

(process:19015): GLib-GObject-CRITICAL **: g_type_class_unref: assertion 'g_class != NULL' failed
/bin/sh: makeself: command not found
Main.make:125: recipe for target 'veracrypt' failed
make[1]: *** [veracrypt] Error 127
Makefile:287: recipe for target 'all' failed
make: *** [all] Error 2

Any Ideas what's going on here?

Commented Unassigned: veracrypt from git will not compile on Manjaro [123]

$
0
0
When ever I try and compile veracrypt from the github version I get the following error message:

Compiling WizardFrame.cpp
Linking veracrypt

(process:19015): GLib-GObject-CRITICAL **: g_type_class_unref: assertion 'g_class != NULL' failed
/bin/sh: makeself: command not found
Main.make:125: recipe for target 'veracrypt' failed
make[1]: *** [veracrypt] Error 127
Makefile:287: recipe for target 'all' failed
make: *** [all] Error 2

Any Ideas what's going on here?
Comments: The error message is self explanatory : you don't have makeself which is needed. Please read the file Readme.txt in the source directory that lists all required dependencies (makeself is among them)

Closed Unassigned: veracrypt from git will not compile on Manjaro [123]

$
0
0
When ever I try and compile veracrypt from the github version I get the following error message:

Compiling WizardFrame.cpp
Linking veracrypt

(process:19015): GLib-GObject-CRITICAL **: g_type_class_unref: assertion 'g_class != NULL' failed
/bin/sh: makeself: command not found
Main.make:125: recipe for target 'veracrypt' failed
make[1]: *** [veracrypt] Error 127
Makefile:287: recipe for target 'all' failed
make: *** [all] Error 2

Any Ideas what's going on here?
Comments: Documented dependency is missing.

New Post: Cloud usage: Store a volume like a file by unencripted file

$
0
0
I think the best way to handle Cloud Encryption is to do a Sparse based container just like the one that can be created in Mac OS X with Disk Utility. A container of X size could be created but the container is split in sectors, splits of around 8Mbs. So whenever a file is modified within the container, the only container files that are really modified are the ones which represent the sector where the modified file is stored.

Created Unassigned: Bootloader Timeout and Cancel Timeout on Key Strike [124]

$
0
0
Diskcryptor has provided a much better Bootloader than Truecrypt for a long time.

The bootloader of Diskcryptor allows:


__Bootloader Timeout:__

The bootloader prompts for a password, for which a timeout can be set
e.g. 3 seconds. If nothing is pressed within 3 seconds, the bootloader continues.

However, if the user strikes a key within 3 seconds, the timeout is cancelled and the bootloader waits until the user has attempted a password.


__Incorrect Password:__

If no password is entered (i.e. timeout) or an incorrect password is entered, the bootloader continues to load the Boot Disk MBR.


It would be very helpful if you can implement this in Veracrypt

(i.e. __timeout and cancel timeout on key strike__)


as it means no need to run both Diskcryptor and Truecrypt which slows system down too much due to dual encryption!


Some screenshots showing Diskcryptor bootloader settings:

Boot Method - http://postimg.org/image/z46j038rt/
Authentication Method - http://postimg.org/image/b2heuqh7h/
What Happens with Invalid/No Password - http://postimg.org/image/ire96ghp9/

Edited Unassigned: Bootloader Timeout and Cancel Timeout on Key Strike [124]

$
0
0
Diskcryptor has provided a much better Bootloader than Truecrypt for a long time.
_
As a background, I have a Dual Boot system - C: is unencrypted but D: is encrypted using full disk encryption. C: is always bootable (unencrypted), but for D: if the password is wrong or no password is given D: will not boot _


The bootloader of Diskcryptor allows:


__Bootloader Timeout:__

The bootloader prompts for a password, for which a timeout can be set
e.g. 3 seconds. If nothing is pressed within 3 seconds, the bootloader continues.

However, if the user strikes a key within 3 seconds, the timeout is cancelled and the bootloader waits until the user has attempted a password.


__Incorrect Password:__

If no password is entered (i.e. timeout) or an incorrect password is entered, the bootloader continues to load the Boot Disk MBR.


It would be very helpful if you can implement this in Veracrypt

(i.e. __timeout and cancel timeout on key strike__)


as it means no need to run both Diskcryptor and Truecrypt which slows system down too much due to dual encryption!


Some screenshots showing Diskcryptor bootloader settings:

Boot Method - http://postimg.org/image/z46j038rt/
Authentication Method - http://postimg.org/image/b2heuqh7h/
What Happens with Invalid/No Password - http://postimg.org/image/ire96ghp9/
Viewing all 7620 articles
Browse latest View live


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