1.17 Beta Release - Feedback or Issues

Topics: Technical Issues
Nov 28, 2015 at 3:32 PM
Edited Nov 28, 2015 at 5:08 PM
If possible, please post your feedback or issues regarding the latest release of beta 1.17 version to the link below to consolidate user responses into one thread on SourceForge.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Dec 3, 2015 at 3:48 PM
Edited Dec 3, 2015 at 3:54 PM
December 2nd, 2015 Beta 1.17 has been released with changes to Linux.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Dec 6, 2015 at 4:13 PM
December 5th, 2015 BETA 1.17 has been released with changes to Windows and MAC OSX.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Dec 17, 2015 at 3:09 AM
December 16th, 2015 BETA 1.17 has been released with changes to Windows.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Dec 21, 2015 at 1:09 PM
December 20th, 2015 BETA 1.17 has been released to allow caching the PIM and updated language XML files.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Jan 6, 2016 at 6:45 PM
January 5th, 2016 BETA 1.17 has been released. Click on the link below to see all the changes.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Jan 6, 2016 at 8:27 PM
Yummy, PIM caching and keyboard shortcut for PIM. Now VC suits me perfectly, I love it! :) Thanks Mounir!
Jan 17, 2016 at 3:21 PM
January 17th, 2016 version 1.17 BETA 16 has been released. Click on the link below to see all the changes.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Jan 18, 2016 at 10:36 PM
January 18th, 2016 version 1.17 BETA 17 has been released. Click on the link below to see all the changes.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Jan 19, 2016 at 5:11 PM
Edited Jan 19, 2016 at 5:22 PM
Whirlpool volumes open way faster now, SHA-512 takes a bit less time than before but not faster than Whirlpool.


I have two volumes with each hash, both with PIM = 500 and Whrilpool opens way faster, SHA-512 with the same iterations takes a bit more time compared to 500 PIM iterations on Whirlpool. Is that OK? I read that there were some optimizations on Whirlpool, is that the reason?



Small extra:

On 'about' section it still says IDRIX 2013-2015.
Coordinator
Jan 19, 2016 at 10:51 PM
You are running VeraCrypt under which OS? Is it 32-bit or 64-bit?

Indeed, there have a major enhancement to Whirlpool thanks to the use of SSE assembly and there was also an overall optimization that cuts mount/boot time for all algorithms by half. This is explained in the release notes: https://veracrypt.codeplex.com/wikipage?title=Release%20Notes

But on all my benchmarks, Whirlpool is always slower than SHA-512. For example, on a Windows 7 64-bit running on a Core-i7 2600K 3GH, here is the output of the script bench.bat available in the source package but also downloadable here:

SHA-512 (Normal) = 00:00:01,86
SHA-512 (Hidden) = 00:00:03,53

Whirlpool (Normal) = 00:00:03,34
Whirlpool (Hidden) = 00:00:06,58

SHA-256 (Normal) = 00:00:02,75
SHA-256 (Hidden) = 00:00:05,30

RIPEMD-160 (Normal) = 00:00:06,16
RIPEMD-160 (Hidden) = 00:00:12,21

Wrong Password (PRF Auto-detection)= 00:00:12,36
Times are in seconds and for 1.17-BETA17. As you can see Whirlpool is slower than SHA-512.

I'm interested to know more about your platform and your benchmark numbers.

Thanks for the date remark...I'll fix it.
Jan 20, 2016 at 9:08 AM
Edited Jan 20, 2016 at 9:24 AM
Hello!

It was a bit weird for me since I have read these benchmarks before. I'm using Windows 7 32-bits, it's a very old desktop computer with 512MB RAM.

I'll try to do that, but if my memory is OK, it takes about 7 seconds for PIM 500 Whirlpool and about twice the time for SHA-512, about 15 seconds. Before this Beta version, it was about 30 seconds SHA-512 and 40 seconds Whirlpool.


SHA-256 is faster than before but still, on 'normal' setup (without even touching PIM, don't know how many iterations) takes almost the same time or a bit more than PIM 500 Whirlpool, about 7 seconds.

Same happens with a PIM 100 Whirlpool and another with PIM 100 SHA-512 volumes, Whirlpool was faster.


I'm not complaining at all, I though it was rare that Whirlpool was faster and used this thread to talk about it. Your amazing work is very appreciated and this version is great since I wait less time opening volumes. Obviously development should be prioritized to fast computers.


Thank you for your answers and help!
Jan 27, 2016 at 2:25 PM
January 27th, 2016 version 1.17 BETA 18 has been released. Click on the link below to see all the changes.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Feb 1, 2016 at 3:19 AM
January 31st, 2016 version 1.17 BETA 19 has been released. Click on the link below to see all the changes.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Feb 9, 2016 at 2:40 PM
February 9th, 2016 version 1.17 BETA 20 has been released. Click on the link below to see all the changes.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Feb 12, 2016 at 12:32 AM
February 11th, 2016 version 1.17 BETA 21 has been released. Click on the link below to see all the changes.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/d36e6405/
Feb 13, 2016 at 7:22 PM
Edited Feb 13, 2016 at 7:23 PM
>Fix leak of path of selected keyfiles in RAM.

Would it be possible to get a little explaination on this? I only ask because on later versions of Windows (I use 8.1), the folder of selected key files also gets logged in ShellNoRoam.

The same is said about folders inside a volume.