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

Created Unassigned: The --stdin option does not work [356]

January 17, 2016, 9:49 am
$
0
0
Just built a NOGUI veracrypt_1.16_Source.tar.bz2 on fedora22 linux, and no power on earth seems to be able to get the --stdin option to work for reading passwords:

```
zooty> sudo veracrypt --non-interactive --protect-hidden=no --pim=0 --hash=sha512 --keyfiles=/huge/secure.keyfile --stdin /huge/secure.hc /secure < passfile
Error: Operation failed due to one or more of the following:
- Incorrect keyfile(s).
- Incorrect password.
- Incorrect Volume PIM number.
- Incorrect PRF (hash).
- Not a valid volume.

```

However, if I use the interactive version, it seems to work fine:

```
zooty> sudo veracrypt --protect-hidden=no --pim=0 --hash=sha512 --keyfiles=/huge/secure.keyfile /huge/secure.hc /secure < passfile
Enter password for /huge/secure.hc:

```

It prints the prompt, but also reads the exact same password file from stdin and mounts the secure filesystem correctly.
↧
Search

Commented Unassigned: A "security Leak". [348]

January 17, 2016, 10:22 am
$
0
0
Veracrypt 1.17 beta remember the location (path) and the name of the last used keyfile. Now, every person that uses my computer knows the last keyfile I used. The Veracrypt 1.16 does not remember that and always takes the user to the home folder. An additional suggestion: like the PIM, there should be an option for caching the HMAC for faster mount.
Comments: @ archfrog I use system encryption so don't have any need for keyfiles and am quite sane, and my comment was to temporary not to use keyfiles in VeraCrypts current state with that bug :p Point taken about multiple people using the same system, anyhow the keyfile is no use without the password, and as several users are using it, all it takes is an uneducated user to compromise the whole system and the passwords or others. Its kind of funny though multiple users using the same machine and using encryption against each other, worrying about keyfile should be the least concern when each user has direct physical access to the machine, anyone could install a key logger or malware, or even get malware form the Internet it could compromise the whole system and the encrypted volumes!!! If your serious about security use defense in depth and avoid the risk of others using your system.
↧
↧

New Post: Changing PIM bug

January 17, 2016, 10:26 am
$
0
0
Since you encrypted the C drive using default PIM, you do not need to enter a value in the Current section or if you do enter a value, the value should be blank or 0 (zero) to use the default. Then in the New section, enter your new PIM value.

By entering the value 1 in the Current section, you are using a non-default value and the reason you are failing to change the PIM.
↧

Commented Unassigned: A "security Leak". [348]

January 17, 2016, 10:37 am
$
0
0
Veracrypt 1.17 beta remember the location (path) and the name of the last used keyfile. Now, every person that uses my computer knows the last keyfile I used. The Veracrypt 1.16 does not remember that and always takes the user to the home folder. An additional suggestion: like the PIM, there should be an option for caching the HMAC for faster mount.
Comments: @ acrchfrog Ignore my comment about the key logger, I overlooked that part before commenting, which I would have deleted it if codeplex allowed it. So it should read this: I use system encryption so don't have any need for keyfiles and am quite sane, and my comment was to temporary not to use keyfiles in VeraCrypts current state with that bug :p Point taken about multiple people using the same system, anyhow the keyfile is no use without the password, and as several users are using it, all it takes is an uneducated user to compromise the whole system and the passwords for others. Its kind of funny though multiple users using the same machine and using encryption against each other, worrying about keyfile should be one concern and another is that each user has direct physical access to the machine, If your serious about security use defense in depth and avoid the risk of others using your system.
↧

Created Unassigned: Error while mounting encrypted partition in Arch Linux [357]

January 18, 2016, 12:44 am
$
0
0
When I try to mount any encrypted partition in Arch Linux, I get following error:
Bad file descriptor
VeraCrypt::CoreService::StartElevated:517
The strange thing is, that this happens only when trying to mount the partition for the first time since computer starts. When trying to do this for the second time, it mounts successfully.
I am running Veracrypt version 1.16. If you need more information, just ask.
↧
↧

Updated Release: VeraCrypt version 1.17-BETA17 (janv. 18, 2016)

January 18, 2016, 2:25 pm
$
0
0

Changes between 1.16 and 1.17-BETA17 (18 January 2016) :

  • All OSs:
    • Support UNICODE passwords: all characters are now accepted in passwords (except Windows system encryption)
    • Cut mount/boot time by half thanks to a clever optimization of key derivation (found by Xavier de Carné de Carnavalet)
  • Windows:
    • Fix dll hijacking issue affecting installer that allows code execution with elevation of privilege (CVE-2016-1281). Reported by Stefan Kanthak (http://home.arcor.de/skanthak/)
    • Sign binaries using both SHA-1 and SHA-256 to follow new Microsoft recommendations.
    • Solve issues under Comodo/Kaspersky when running an application from a VeraCrypt volume (Reported and fixed by Robert Geisler)
    • Bootloader: Protect password/PIM length by filling the fields to maximum length with '*' after ENTER
    • Solve issue with system favorites not being able to be mounted to drive A:
    • Solve lost focus issues for after displaying the waiting dialog
    • Implement PIM caching, for both system encryption and normal volumes. Add options to activate it.
    • Internal rewrite to make VeraCrypt native UNICODE application.
    • Workaround to avoid false positive detection by some anti-virus software.
    • Hide disconnected network drives in the list of available drives. Add option to make them available for mounting.
    • Solve issue that caused in some cases configuration and history XML files to be updated even when not needed.
    • Fix leak of path of selected keyfiles in RAM.
    • Fix TB unit can't be deselected in VeraCryptExpander.
    • Add Alt+i keyboard shortcut for "Use PIM" checkbox.
    • Minor GUI and translations fixes.
↧

Commented Unassigned: Volume Expander cancel warning [358]

January 18, 2016, 2:31 pm
$
0
0
While working with the Beta version 1.17 BETA15 of Veracrypt I noticed a cancel warning combined with some asian letters right after starting the expansion process. Also the progress bar is frozen at 100% right from the start.
Comments: Thank you for reporting this. I have [fixed this issue](https://veracrypt.codeplex.com/SourceControl/changeset/484289cdbda99027bcd905d9c79c72c0a51b694e) and I uploaded a new installer for 1.17-BETA17 that includes this fix. It can be found here: https://veracrypt.codeplex.com/releases/view/619351 Closing this issue. Don't hesitate to post any problems you may encounter.
↧

Closed Unassigned: Volume Expander cancel warning [358]

January 18, 2016, 2:32 pm
$
0
0
While working with the Beta version 1.17 BETA15 of Veracrypt I noticed a cancel warning combined with some asian letters right after starting the expansion process. Also the progress bar is frozen at 100% right from the start.
↧
Search

Edited Issue: Volume Expander cancel warning [358]

January 18, 2016, 2:32 pm
$
0
0
While working with the Beta version 1.17 BETA15 of Veracrypt I noticed a cancel warning combined with some asian letters right after starting the expansion process. Also the progress bar is frozen at 100% right from the start.
↧
↧

Commented Unassigned: Possible beta 16 hdd fail [359]

January 18, 2016, 2:43 pm
$
0
0
This could be totally coincidental but I've just upgraded from beta 15 to 16 and after the prompt to restart immediately I didn't, and 5 mins later while in Chrome the screen went blank and my laptop froze. I powered off and on and nothing happens-screen doesn't power up, hdd isn't accessed and no num/caps/hdd activity lights turn on-i can't boot even into bios.

Now, I'm sure it's not related to VC but I'm just posting this in case anyone else has similar problems. I literally have a dead laptop-I'll be buying a new one at the weekend ><
Comments: The update process only replaces files and it doesn't interact in any way with encrypted volumes or the encrypted system. Thus, I don't see how updating the software could lead to a hdd failure on its own! In my opinion, your hard drive was the verge of failure and writing new VeraCrypt files was the straw that broke the camel's back (in French I would say la goutte qui fait déborder le vase). Anyway, I'm not sure if it is worth opening an issue on the tracker...but I'll keep it open for now although there will be no action.
↧

Commented Unassigned: Error while mounting encrypted partition in Arch Linux [357]

January 18, 2016, 3:06 pm
$
0
0
When I try to mount any encrypted partition in Arch Linux, I get following error:
Bad file descriptor
VeraCrypt::CoreService::StartElevated:517
The strange thing is, that this happens only when trying to mount the partition for the first time since computer starts. When trying to do this for the second time, it mounts successfully.
I am running Veracrypt version 1.16. If you need more information, just ask.
Comments: It appears that for some reason the output pipe that connects VeraCrypt with the forked "sudo" process becomes invalid...this is not supposed to happen! Moreover, it appears only the first time "sudo" is called after computer start...this is definitely not a VeraCrypt issue but something on the Linux Kernel that causes this pipe failure the first time after boot. We can imagine implementing a workaround in VeraCrypt to retry the "sudo" fork when this happens but this is not the correct approach because the underlying system should behave correctly. Just to verify, can you check if the forked "sudo" process exists when the error occurs?
↧

New Post: 1.17 Beta Release - Feedback or Issues

January 18, 2016, 3:36 pm
↧

Updated Wiki: Release Notes

January 18, 2016, 3:38 pm
$
0
0

Release Notes

1.17-BETA17 (January 18th, 2016):

  • All OSs:
    • Support UNICODE passwords: all characters are now accepted in passwords (except Windows system encryption)
    • Cut mount/boot time by half thanks to a clever optimization of key derivation (found byXavier de Carné de Carnavalet)
    • Optimize Whirlpool PRF speed by using assembly (25% speed gain compared to previous code).
    • Include new icons and graphics contributed by Andreas Becker (http://www.andreasbecker.de)
  • Windows:
    • Fix dll hijacking issue affecting installer that allows code execution with elevation of privilege (CVE-2016-1281). Reported by Stefan Kanthak (http://home.arcor.de/skanthak/)
    • Sign binaries using both SHA-1 and SHA-256 to follow new Microsoft recommendations.
    • Solve Kaspersky 2016 crash and Comodo Antivirus read-only issues when running applications from a VeraCrypt volume (Reported and fixed byRobert Geisler).
    • Bootloader: Protect password/PIM length by filling the fields to maximum length with '*' after ENTER
    • Solve issue with system favorites not being able to be mounted to drive A:
    • Solve lost focus issues for after displaying the waiting dialog
    • Implement PIM caching, for both system encryption and normal volumes. Add option to activate it.
    • Internal rewrite to make VeraCrypt native UNICODE application.
    • Workaround to avoid false positive detection by some anti-virus software.
    • Hide disconnected network drives in the list of available drives. Add option to make them available for mounting.
    • Solve issue that caused in some cases configuration and history XML files to be updated even when not needed.
    • Fix leak of path of selected keyfiles in RAM.
    • Fix TB unit can't be deselected in VeraCryptExpander.
    • Add Alt+i keyboard shortcut for "Use PIM" checkbox in GUI.
    • Minor GUI and translations fixes.

1.16 (October 7th, 2015):

  • Windows:
    • Modify patch for CVE-2015-7358 vulnerability to solve side effects on Windows while still making it very hard to abuse drive letter handling.
    • Fix failure to restore volume header from an external file in some configurations.
    • Add option to disable “Evil Maid” attack detection for those encountering false positive cases (e.g. FLEXnet/Adobe issue).
    • By default, don’t try to mount using empty password when default keyfile configured or keyfile specified in command line. Add option to restore the old behavior.
      • If mounting using empty password is needed, explicitly specify so in the command line using: /p ""

1.15 (September 26th, 2015):

  • Windows:
    • Fix two TrueCrypt vulnerabilities reported by James Forshaw (Google Project
      Zero)
      • CVE-2015-7358 (critical): Local Elevation of Privilege on Windows by
        abusing drive letter handling.
      • CVE-2015-7359: Local Elevation of Privilege on Windows caused by
        incorrect Impersonation Token Handling.
    • Fix regression in mounting of favorite volumes at user logon.
    • Fix display of some Unicode languages (e.g. Chinese) in formatting wizard.
    • Set keyboard focus to PIM field when "Use PIM" is checked.
    • Allow Application key to open context menu on drive letters list
    • Support specifying volumes size in TB in the GUI (command line already supports this)

1.14 (September 16th, 2015):

  • All OSs:
    • Mask and unmask PIM value in GUI and bootloader like the password.
  • Windows:
    • Solve Rescue Disk damaged error when using cascade ciphers and SHA256 for system encryption.
    • Solve option "Cache password in drive memory" always disabled even if checked in preferences.
    • Solve UI language change not taken into account for new install unless a preference is changed.
    • Implement creating file containers using command line.
    • Driver: disable support of IOCTL_STORAGE_QUERY_PROPERTY by default and add option to enable it.
    • Driver:  Support returning StorageDeviceProperty when queried through IOCTL_STORAGE_QUERY_PROPERTY.
    • Support setting volume label in Explorer through mount option or favorite label value.
    • Fix for Hot Keys assignment dialog issue where OEM-233 is always displayed and can't be changed.
    • Always copy both 32-bit and 64-bit executable binaries during install and in Traveler Disk Setup.
      • Traveler Disk will again use 32-bit exe by default while also offering 64-bit exe.
      • On Windows 64-bit, 32-bit exe files are now available(e.g. if needed to use 32-bit PKCS#11 dll)
    • Include Volume Expander in Traveler Disk Setup.
    • Don't offer creating a restore point if it is disabled in Windows.
    • Add possibility to verify a Rescue Disk ISO image file.
    • Minors fixes in the installer, GUI and driver.
  • Linux:
    • Support supplying password using stdin in non interactive mode (contributed byLouisTakePILLz)
      • Example: veracrypt -t ${IMAGE_PATH} ${MOUNT_PATH} --mount --non-interactive --stdin <<< "$PWD"

1.13 (August 9th, 2015):

  • Windows:
    • Solve TOR crashing when run from a VeraCrypt volume.

1.12 (August 5th, 2015):

  • All OSs:
    • Implement "Dynamic Mode" by supporting a Personal Iterations Multiplier (PIM). See documentation for more information.
  • Windows:
    • Detect Boot Loader tampering ("Evil Maid" attacks) for system encryption and propose recovery options.
    • Fix buffer overrun issue and other memory related bugs when parsing language XML files.
    • Fix wrongly reported bad sectors by chkdsk caused by a bug in IOCTL_DISK_VERIFY handling.
    • Fix privacy issue caused by configuration and history files being updated whenever VeraCrypt is used (reported by Liran Elharar)
    • Fix system favorites not always mounting after cold start.
    • Solve installer error when updating VeraCrypt on Windows 10.
    • Implement decryption of non-system partition/drive.
    • Include 64-bit exe files in the installer and deploy them on 64-bit machines for better performances.
    • Allow using drive letters A: and B: for mounting volumes
    • Make command line argument parsing more strict and robust (e.g. /lz rejected, must be /l z)
    • Add possibility to show system encryption password in Windows GUI and bootloader
    • Solve "Class Already exists" error that was happening for some users.
    • Solve some menu items and GUI fields not translatable
    • Make volumes correctly report Physical Sector size to Windows.
    • Correctly detect switch user/RDP disconnect operations for autodismount on session locked.
    • Add manual selection of partition when resuming in-place encryption.
    • Add command line option (/cache f) to temporarily cache password during favorites mounting.
    • Add waiting dialog for Auto-Mount Devices operations to avoid freezing GUI.
    • Add extra information to displayed error message in order to help analyze reported issues.
    • Disable menu entry for changing system encryption PRF since it's not yet implemented.
    • Fix failure to change password when UAC required (inherited from TrueCrypt)
    • Minor fixes and changes (see Git history for more details)
  • Linux:
    • Solve installer issue under KDE when xterm not available
    • Fix warnings on about/LegalNotice dialogs when wxWidgets linked dynamically (N/A for official binary)
    • Support hash names with '-' in command line (sha-256, sha-512 and ripemd-160)
    • Remove "--current-hash" switch and add "--new-hash" to be more coherent with existing switches.
    • When only keyfile specified in command line, don't try to mount using empty password.
      • If mounting using empty password is needed, explicitly specify so using: -p ""

1.0f-2(April 5th, 2015):

  • All OSs:
    • Mounting speed improvement, up to 20% quicker on 64-bit (contributed by Nils Maier)
    • Add option to set default hash/TrueCryptMode used for mounting volumes.
    • Use TrueCryptMode/Hash specified in command line in password dialog.
  • Windows:
    • Solve CryptAcquireContext vulnerability reported by Open Crypto Audit Phase II.
    • Proper handling of random generator failures. Inform user in such cases.
    • TrueCrypt Mode related changes:
      • Support mounting TrueCrypt system partition (no conversion yet)
      • Support TrueCrypt volumes as System Favorites.
      • Correct displaying wrong TrueCrypt mode in volume properties when SHA-256 is used.
    • Solve PIN BLOCKED issue with smart cards in a special case.
    • Correctly handle file access errors when mounting containers.
    • Solve several issues reported by the Static Code Analysis too Coverity.
    • Bootloader: Add "Verifying Password..." message.
    • When UAC prompt fails (for example timeout), offer the user to retry the operation.
    • Uninstall link now open the standard "Add/Remove Programs" window.
    • On uninstall, remove all VeraCrypt references from registry and disk.
    • Included VeraCryptExpander in the Setup.
    • Add option to temporary cache password when mounting multiple favorites.
    • Minor fixes and enhancements (see git history for more information)
  • MacOSX:
    • Solve issue volumes not auto-dismounting when quitting VeraCrypt.
    • Solve issue VeraCrypt window not reopening by clicking dock icon.
  • Linux/MacOSX:
    • Solve preferences dialog not closing when clicking on the 'X' icon.
    • Solve read-only issue when mounting non-FAT volumes in some cases.
    • Support opening/exploring mounted volumes on desktops other than Gnome/KDE.
    • Solve various installer issues when running on less common configurations
    • Minor fixes (see git history for more information)

1.0f-1 (January 4th, 2015)

  • All OSs:
    • Add support for old TrueCrypt 6.0.
    • Change naming of cascades algorithms in GUI for a better description.
  • Linux/MacOSX:
    • Make cancel button of the preference dialog working.
    • Solve impossibility to enter a one digit size for the volume.
    • Add wait dialog to the benchmark calculation.
  • Windows:
    • Add TrueCrypt mode to the mounted volume information.
    • For Windows XP, correct the installer graphical artefacts.

1.0f (December 30, 2014)

  • All OSs:
    • Add support for mounting TrueCrypt volumes.
    • Add support for converting TrueCrypt containers and non-system partitions.
    • Add support for SHA-256 for volume encryption.
    • Make SHA-512 the default key derivation algorithm and change the order of preference of derivation algorithms : SHA-512 -> Whirlpool -> SHA-256 -> RIPEMD160
    • Deprecate RIPEMD160 for non-system encryption.
    • Speedup mount operation by enabling choice of correct hash algorithm.
    • Display a wait dialog during lengthy operations to avoid freezing the GUI.
    • Implement creation of multiple keyfiles at once, with predefined or random size.
    • Always display random gathering dialog before performing sensitive operations.
    • Links in the application now points to the online resources on Codeplex
    • First version of proper VeraCrypt User Guide
  • MacOSX:
    • Implement support for hard drives with a large sector size (> 512).
    • Link against new wxWidgets version 3.0.2.
    • Solve truncated text in some Wizard windows.
  • 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.
    • Correct a random crash when clicking the link for more information on keyfiles
    • Implement option to auto-dismount when user session is locked
    • Add self-test vectors for SHA-256
    • Modern look-and-feel by enabling visual styles
    • few minor fixed.
1.0e (September 4, 2014)
  • Improvements and bug fixes:
    • 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 improvements and bug fixes (look at git history for more details).

1.0d (June 3, 2014)
  • Improvements and bug fixes:
    • Correct issue while creating hidden operating system.
    • Minor improvements and bug fixes.
↧
↧

Commented Unassigned: The --stdin option does not work [356]

January 18, 2016, 3:52 pm
$
0
0
Just built a NOGUI veracrypt_1.16_Source.tar.bz2 on fedora22 linux, and no power on earth seems to be able to get the --stdin option to work for reading passwords:

```
zooty> sudo veracrypt --non-interactive --protect-hidden=no --pim=0 --hash=sha512 --keyfiles=/huge/secure.keyfile --stdin /huge/secure.hc /secure < passfile
Error: Operation failed due to one or more of the following:
- Incorrect keyfile(s).
- Incorrect password.
- Incorrect Volume PIM number.
- Incorrect PRF (hash).
- Not a valid volume.

```

However, if I use the interactive version, it seems to work fine:

```
zooty> sudo veracrypt --protect-hidden=no --pim=0 --hash=sha512 --keyfiles=/huge/secure.keyfile /huge/secure.hc /secure < passfile
Enter password for /huge/secure.hc:

```

It prints the prompt, but also reads the exact same password file from stdin and mounts the secure filesystem correctly.
Comments: I think I see what is going on here. Check out: [this stackoverflow post](http://stackoverflow.com/questions/5838711/c-cin-input-with-spaces) The --stdin option doesn't work with a password that contains spaces (and experimental evidence seems to agree). I guess the interactive mode reads stdin differently, because spaces work fine there.
↧

New Post: How to recover encrypted drive

January 18, 2016, 5:00 pm
$
0
0
Hi,

I have had the longest night trying to recover my encrypted drive, with the only set of my most important documents. I'm inbetween a rock and a hard place, not being able to work, or take care of extremely critical tasks. I know - was going to run a new backup in just 2 days from now...

Here's what happened:
  1. I could not load Windows 10 and tried to run Startup Recovery, which stalled and rebooted
  2. Used Paragon Recovery Tools and unfortunately chose REBUILD MBR FOR ALL DRIVES !!!
  3. Having corrupted the encrypted drived by creating an MBR on it I deleted the partition
  4. As I could still not mount the encrypted drive I ran DISKPART and CLEAN on it
I check "Use backup header embedded in volume, if availble", but it fails to mount.

I would be most grateful for any advice on what to do, as I'm a newbie to encryption.

Kindly,
Kaliya
↧
Search

New Post: HELP - URGENT: I Cannot Mount My Encrypted Drive !!!

January 18, 2016, 5:06 pm
$
0
0
I have had the longest night trying to recover my encrypted drive, with the only set of my most important documents. I'm inbetween a rock and a hard place, not being able to work, or take care of extremely critical tasks. I know - was going to run a new backup in just 2 days from now...

Here's what happened:
  1. I could not load Windows 10 and tried to run Startup Recovery, which stalled and rebooted
  2. Used Paragon Recovery Tools and unfortunately chose REBUILD MBR FOR ALL DRIVES !!!
  3. Having corrupted the encrypted drived by creating an MBR on it I deleted the partition
  4. As I could still not mount the encrypted drive I ran DISKPART and CLEAN on it
I check "Use backup header embedded in volume, if availble", but it fails to mount.

I would be most grateful for any advice on what to do, as I'm a newbie to encryption.

Kindly,
Kaliya
↧

Commented Unassigned: The --stdin option does not work [356]

January 18, 2016, 5:11 pm
$
0
0
Just built a NOGUI veracrypt_1.16_Source.tar.bz2 on fedora22 linux, and no power on earth seems to be able to get the --stdin option to work for reading passwords:

```
zooty> sudo veracrypt --non-interactive --protect-hidden=no --pim=0 --hash=sha512 --keyfiles=/huge/secure.keyfile --stdin /huge/secure.hc /secure < passfile
Error: Operation failed due to one or more of the following:
- Incorrect keyfile(s).
- Incorrect password.
- Incorrect Volume PIM number.
- Incorrect PRF (hash).
- Not a valid volume.

```

However, if I use the interactive version, it seems to work fine:

```
zooty> sudo veracrypt --protect-hidden=no --pim=0 --hash=sha512 --keyfiles=/huge/secure.keyfile /huge/secure.hc /secure < passfile
Enter password for /huge/secure.hc:

```

It prints the prompt, but also reads the exact same password file from stdin and mounts the secure filesystem correctly.
Comments: ...And this patch makes it work correctly by using getline: ``` --- src/Main/UserInterface.cpp.orig 2016-01-18 19:56:06.301994775 -0500 +++ src/Main/UserInterface.cpp 2016-01-18 19:58:40.542297822 -0500 @@ -894,8 +894,10 @@ if (Preferences.UseStandardInput) { + wchar_t pwdLine[1024]; wstring pwdInput; - wcin >> pwdInput; + wcin.getline(pwdLine, sizeof(pwdLine)); + pwdInput.append(pwdLine); cmdLine.ArgPassword = make_shared<VolumePassword> (pwdInput); } ```
↧
↧

Commented Unassigned: The --stdin option does not work [356]

January 18, 2016, 5:30 pm
$
0
0
Just built a NOGUI veracrypt_1.16_Source.tar.bz2 on fedora22 linux, and no power on earth seems to be able to get the --stdin option to work for reading passwords:

```
zooty> sudo veracrypt --non-interactive --protect-hidden=no --pim=0 --hash=sha512 --keyfiles=/huge/secure.keyfile --stdin /huge/secure.hc /secure < passfile
Error: Operation failed due to one or more of the following:
- Incorrect keyfile(s).
- Incorrect password.
- Incorrect Volume PIM number.
- Incorrect PRF (hash).
- Not a valid volume.

```

However, if I use the interactive version, it seems to work fine:

```
zooty> sudo veracrypt --protect-hidden=no --pim=0 --hash=sha512 --keyfiles=/huge/secure.keyfile /huge/secure.hc /secure < passfile
Enter password for /huge/secure.hc:

```

It prints the prompt, but also reads the exact same password file from stdin and mounts the secure filesystem correctly.
Comments: Wups, forgot about std::getline. Here is a smaller patch that works better and has no line length limitation: ``` --- src/Main/UserInterface.cpp.orig 2016-01-18 20:24:14.048169627 -0500 +++ src/Main/UserInterface.cpp 2016-01-18 20:24:36.518793210 -0500 @@ -895,7 +895,7 @@ if (Preferences.UseStandardInput) { wstring pwdInput; - wcin >> pwdInput; + getline(wcin, pwdInput); cmdLine.ArgPassword = make_shared<VolumePassword> (pwdInput); } ```
↧

New Post: Cloud: Split File Containers into small files.

January 19, 2016, 1:00 am
$
0
0
testoslav wrote:
Having the possibility to span a container across multiple files would be nice, but has nothing to do with cloud storage. Just pick a cloud storage with rsync support ;-)
You completely went off topic, the idea is not to find another cloud storage that supports something else, the idea is to be able to use any of the standard ones, like Dropbox or Google Drive.

If I have a veracrypt container of let's say, 20Gbs, which happens to be split into multiple files of smaller size, like 5Mbs. If I modify something within the 20Gbs container, only the disk sectors that were modified are the ones that will be re-uploaded to the cloud, rather than having to re-upload 20Gbs.

RandomNameforCode wrote:
At least DropBox uses Delta-Sync:

https://www.dropbox.com/business/sync-performance
I don't think the delta sync applies for any type of file. But I'll test anyways
↧

New Post: Same letter for non-system partition

January 20, 2016, 12:02 am
$
0
0
I have encrypted partition with letter (e.g.) X.

When I mount this partition with VeraCrypt, it is assigned a different letter (e.g.) Y.

So, encrypted partition occupies two letters.
Is it designed this way or am I doing something wrong?
I would expect that encrypted partition would use the same letter after encryption.
↧
Viewing all 7620 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>