Menu

1.17 Beta Release - Feedback or Issues

2015-11-28
2016-03-04
  • Mounir IDRASSI

    Mounir IDRASSI - 2015-11-28

    Please post your feedback or issues regarding the latest release of beta 1.17 version to this thread.

    2016.02.11 Beta 21 of 1.17 has been released with the following changes:

    • Windows: Avoid updating configuration after opening keyfile file dialog when /quit switch used without preferences parameter.
    • Windows: Fix regression that caused only a single keyfile to be taken into account.
    • Windows: Add colors (Red, Yellow, Green) to the collected randomness indicator depending on how much entropy was gathered. Code re-factoring.

    2016.02.09 Beta 20 of 1.17 has been released with the following changes:

    • Windows: Don't try to mount using cached passwords if password and/or keyfile are specified in the command line.
    • Windows: Fix various issues and warnings reported by static code analysis tool Coverity.
    • Windows: Continuation of fix for wrong update of configuration XML file.
    • Windows Driver: If saving volume header fails, don't mark operation as successful so that it will be retried later.
    • Linux/MacOSX: Add progress bar for mouse collected entropy in GUI for keyfile generator and for random poll enrichment.
    • Linux/MacOSX: Add progress bar for mouse collected entropy in GUI of volume creation wizard. Add mutex protection in event handler for shared counter variable.
    • Language Files: Update German and Polish translations.

    2016.01.31 Beta 19 of 1.17 has been released with the following changes:

    • Windows Bootloader: Always hide password/PIM values with asterisks after ENTER is hit, even if F5 was pressed to display password/PIM.
    • Windows: Implement GUI indicator for entropy collected from mouse movements.
    • Windows: Center the text of the random pool displayed in the keyfile generator dialog.
    • Windows: Fix buffer overrun issue introduce by the Unicode rewrite.
    • Windows: Fix link issue in Debug configuration for Setup project.
    • Windows: solve bootloader compilation error.
    • MacOSX: Support creation exFAT volumes on OSX using the built-in command newfs_exfat.
    • Language XML files: Updated message translation in Chinese, German, Korea, Polish and Russian.
    • Language XML files: update XML files with newly added field.

    2016.01.27 Beta 18 of 1.17 has been released with the following changes:

    • Copyright: update dates to include 2016.
    • Windows: hide PIM is VeraCrypt Expander the same way as in other places.
    • Windows: Fix issue with the display of legal notices text. Regression caused by the latest Unicode modifications.
    • Windows and Linux: Add support for creating exFAT volumes (Windows and Linux).
    • Linux/MacOSX: Fix issue of --stdin option not handling correctly passwords that contain a space character (reported and fixed by Codeplex user horsley1953).
    • Linux/MacOSX: Fix issue creating volumes using command line with a filesystem other than FAT.
    • Linux/MacOSX: Support K/M/G/T suffixes for --size switch to indicate unit to use for size value.
    • Linux/MacOSX: Update command line help text to reflect that we can now specify in filesystem when creating a new volume.
    • Linux/MacOSX: fix wrong AskYesNo method parameters use caused by mistake in parenthesis use.
    • Linux/MacOSX: update --size entry in command line help text.
    • MacOSX: Add PIM value validity checks to workaround wxWidget bug that makes wxTextValidator useless when applied to a text control with password attribute (http://trac.wxwidgets.org/ticket/17185).

    2016.01.18 Beta 17 of 1.17 has been released with the following changes:

    • Windows: solve Expander GUI issues caused by latest Unicode modifications.

    2016.01.16 Beta 16 of 1.17 has been released with the following changes:

    • Windows: avoid leaking location of selected keyfiles by clearing global variable used to store multiple file selection path.
    • All OSs: Divide mount and boot times by 2 using a pre-computation of values used in PRF HMac calculation (thanks to Xavier de Carné de Carnavalet for finding this optimization).
    • Windows: Add SHA-256 EV Code Signing using the new GlobalSign certificate on top of the SHA-1 code signing. Create new SHA256 test code signing certificate and update test signing script.
    • MacOSX: use native OSX byte swapping routines used in hash functions to improve speed.
    • Linux/MacOSX: Show better error message when the PKCS#11 library can't be loaded.
    • Windows: Avoid wrong update of configuration XML file caused by not using the correct window handle to get some GUI fields content.
    • Windows: Don't show disconnected network drives in the list of available drives. Add option to make them available for mounting if needed.

    2016.01.05 Beta 1.17 has been released with the following changes:

    • Windows: increase the size of the field IDC_PREF_CACHE_PIM in the preferences dialog to avoid truncation when using a language other then English.
    • Windows: Enhance fix for dll hijacking vulnerability affecting installer (CVE-2016-1281)
    • Windows: Add keyboard shortcut alt+i for checking "Use PIM" in various dialogs like password dialog.
    • Windows: use compiler intrinsic for some functions used in cryptographic primitives to ensure maximum performance.
    • Windows: sign binaries using both SHA-1 and SHA-256 for maximum compatibility. Add requirement for Windows SDK 8.1 that contains signtool.exe version that enables this.
    • Windows: Make benchmark batch file run a PRF measurement only when associated container file is present.
    • Windows Driver: Remove unwanted ':' character at the end of volume device name. This was causing a crash in Kaspersky Internet Security 2016 when a program is run from a VeraCrypt volume.
    • Windows Driver: wipe cached PIM values when passwords are wiped.
    • Linux: Restore Nautilus fix that was mistakenly removed by Whirlpool optimization commit.
    • Cryptography: Set 16-byte alignment for KEY_INFO structure that is used as input for Whirlpool hash. This helps improve performance.
    • Cryptography: correct Whirlpool compilation error on Big Endian platforms.
    • Cryptography: Optimize Whirlpool implementation by using public domain assembly code developed by Wei Dai.

    2015.12.20 Beta 1.17 has been released with the following changes:

    • Windows: Wipe cached PIM values when passwords are wiped.
    • Windows: Implement PIM caching, both for system encryption and for normal volumes. Add options to activate it in the Preferences and System Settings.
    • Language XML files: update XML files with newly added fields.

    2015.12.16 Beta 1.17 has been released with the following changes:

    • Windows: Solve issue with system favorites not being able to be mounted to drive A:

    2015.12.05 Beta 1.17 has been released with the following changes:

    • MacOSX: Support UNICODE passwords: all characters are now accepted in passwords.
    • MacOSX: Include new icons contributed by Andreas Becker (https://github.com/andreas-becker)

    • Windows Rescue Disk: When decryption paused/finished, display message to indicate that header is being updated.

    • Windows: Correct issue with some of new bitmaps that didn't render correctly.
    • Windows: Use new icons an graphics contributed by Andreas Becker (https://github.com/veracrypt/VeraCrypt/issues/9#issuecomment-118353850)

    2015.12.02 Beta 1.17 has been released with the following changes:

    • Linux: Support UNICODE passwords: all characters are now accepted in passwords.
    • Linux: Fix Nautilus not detected as file manager on some Gnome based destributions.
    • Linux: Include new icons contributed by Andreas Becker (https://github.com/andreas-becker)

    2015.11.26 beta 1.17 has been released with the following changes:

    • Windows: Full UNICODE rewrite and implement support for UNICODE passwords.
    • Windows: Solve GUI issues caused by using ANSI string instead of UNICODE ones. Remove Unused functions.
    • Windows: Support creating Traveler Disk when running in Portable Mode
    • Windows: solve crash caused by system function FormatMessage failure on rare cases.
    • Windows Bootloader: Avoid displaying empty new line between password and PIM after filling password field with dummy * characters.
    • Windows Driver: solve compilation error in Debug build caused by a missing variable.
    • Updated language files.

    Previous changes made to 1.17 beta are:

    • Windows Bootloader: Protect password/PIM length by filling the fields to maximum length with * after ENTER
    • Windows: Solve lost focus issues for after displaying the waiting dialog
    • Windows: Workaround to avoid false positive detection by some anti-virus software.
    • Windows: Fix TB unit can't be deselected in VeraCryptExpander.
    • Windows: Minor GUI and translations fixes.
     

    Last edit: Enigma2Illusion 2016-02-12
  • Enigma2Illusion

    Enigma2Illusion - 2015-12-03

    December 2nd, 2015 Beta 1.17 has been released with changes to Linux. See the first post for details.

     

    Last edit: Enigma2Illusion 2015-12-03
  • Enigma2Illusion

    Enigma2Illusion - 2015-12-06

    December 5th, 2015 BETA 1.17 has been released with changes to Windows and MAC. See the first post for details.

     
  • Mounir IDRASSI

    Mounir IDRASSI - 2015-12-16

    December 16th, 2015 BETA 1.17 has been released to fix an issue under Windows that made it impossible to mount system favorites on drive A:

     
  • Enigma2Illusion

    Enigma2Illusion - 2015-12-21

    December 20th, 2015 BETA 1.17 has been released to allow caching the PIM and updated language XML files.

     
  • Enigma2Illusion

    Enigma2Illusion - 2016-01-06

    January 5th, 2016 BETA 1.17 has been released. Please see first post for the list of changes.

     
    • Andreas Boehlk

      Andreas Boehlk - 2016-01-07

      Something wrong!?. On January 5th, 2016 BETA 1.17.13 released, but on January 4th, 2016 BETA 1.17.13 was released the first time and they are not identical neither the sig-files. Anything wrong with the versioning and what are the differences?

       
      • Mounir IDRASSI

        Mounir IDRASSI - 2016-01-07

        The two installers copies the same binaries (version 1.17.3): the installer was rebuilt on January 5th to include the corrected Polish language XML file.

        I didn't increment the version because it affects only the installer and I didn't do any recompilation: the binaries copied are the same. You can check that both installer copy the same binaries.

         
  • murphy

    murphy - 2016-01-09

    Where can I see the exact build number?
    My VeraCrypt only reports 1.17-BETA (64-bit) and the release date.
    (however, I have downloaded and installed it today)

    An issue not worth opening an individual thread, probably not new to 1.17-BETA but existent before:

    The VC drive list doesn't recognize mapped, but disconnected network drives.
    As soon as a network drive is connected, the relevant drive letter disappears.
    Before that, chances are that drive letters already being in use are "misused"
    (happened to me several times today, working with up to five network shares).

     

    Last edit: murphy 2016-01-09
    • Mounir IDRASSI

      Mounir IDRASSI - 2016-01-10

      The build number can be found in the file version of any of the binaries (for example 1.7.13).
      That being said, to make things clearer, I will now display the build number is the About dialog ("VeraCrypt 1.17-BETA14"). I have uploaded a new 1.17-BETA installer (build 14) that include this.

      Concerning disconnected network mapped drives, this is indeed something that is not taken into account and indeed it can cause problems. I will see how I can implement a detection mechanism for them to avoid such misuse errors.
      Thank you for reporting this.

       
    • Mounir IDRASSI

      Mounir IDRASSI - 2016-01-11

      I have done a modification to avoid displaying letters associated with disconnectd network shares. I also added an option for those who neverthless want to be able to use such drive letters.
      I have uploaded 1.17-BETA (Build 15) to Codeplex since Sourceforge is on readonly mode since yesterday. Here is the link: https://veracrypt.codeplex.com/releases/view/619351

      Thank you again for your report.

       

      Last edit: Mounir IDRASSI 2016-01-11
  • Mounir IDRASSI

    Mounir IDRASSI - 2016-01-17

    Beta 16 of 1.17 has been released on January 16th 2016 and it brings a big performance enhancement for mount/boot operations (time cut by half).
    Please see first post for the list of changes.

     
  • Enigma2Illusion

    Enigma2Illusion - 2016-01-18

    Beta 17 of 1.17 has been released on January 18th, 2016.

    Windows: solve Expander GUI issues caused by latest Unicode modifications.

     
  • Enigma2Illusion

    Enigma2Illusion - 2016-01-27

    January 27th, 2016 version 1.17 BETA 18 has been released. Please see first post for the list of changes.

     
  • Enigma2Illusion

    Enigma2Illusion - 2016-02-01

    January 31st, 2016 version 1.17 BETA 19 has been released. Please see first post for the list of changes.

     
  • Enigma2Illusion

    Enigma2Illusion - 2016-02-09

    February 9th, 2016 version 1.17 BETA 20 has been released. Please see first post for the list of changes.

     
  • WRVC2016

    WRVC2016 - 2016-02-11

    Is it ok that I also submit this as an issue?

    https://sourceforge.net/p/veracrypt/discussion/technical/thread/393905b7/
    Mounir, I have extracted and tested 1.17-BETA20 for several hours. Issue is still there. Fortunately, I was able to pinpoint it for you to review.

    It is the command line switch of "/quit". Please review the below.

    No Error:
    "C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /quit background /keyfile "C:\TestArea\KeyFile.txt" /hash "SHA512" /PIM 888 /Password "1234"

    No Error:
    "C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q"

    No Error:
    "C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /keyfile "C:\TestArea\KeyFile.txt" /hash "SHA512" /PIM 888 /Password "1234"

    ERROR: When open KeyFile dialogbox and press OK, it will reset the configuration.xml back to default, causing the lost of all previous settings.
    "C:\TestArea\VeraCrypt-x64.exe" /beep /cache n /history n /wipecache /volume "C:\TestArea\Test.vc" /letter "Q" /quit background

     
  • Mounir IDRASSI

    Mounir IDRASSI - 2016-02-11

    I have fixed this issue in Git. I will upload the installer for 1.17-BETA20 shortly.

    Concerning the Codeplex issue mentionned by Enigma2Illusion above (https://veracrypt.codeplex.com/workitem/354), I can't reproduce it since I can add/select as much files as I want.
    Can you reproduce it on your side?

     
  • Enigma2Illusion

    Enigma2Illusion - 2016-02-12

    February 11th, 2016 version 1.17 BETA 21 has been released. Please see first post for the list of changes.

     
  • WRVC2016

    WRVC2016 - 2016-02-12

    "Can you reproduce it on your side?"

    If you are asking me Mounir, I will test it out later and let you know.

     
  • BZekanovic

    BZekanovic - 2016-03-04

    I've upgrade couple of computers to VeraCrypt 1.17 and I noticed a small bug on the initial password verification procedure. Here is a scenario to what happens and how to get around the issue.

    1. User reboots their computer first time after the upgrade completes or just a random reboot
    2. VeraCrypt 1.17 prompts the user to enter their password and PIM
    3. User enters the required information, but VeraCrypt rejects the password
    4. User selects F5 to see the actual password being entered
    5. User enters the required information, but VeraCrypt rejects the password again

    Workaround

    1. Completely shut down the computer
    2. Turn the computer back on
    3. Using the same password VeraCrypt rejected works this time.

    This only happens when rebooting the computer and it's not consistent.
    Any idea on what could cause this issue?

    Thanks guys,

     

Log in to post a comment.