Florian Schwarz

Invalid due to usage of outdated VeraCrypt 1.23. Prefix naming is fixed in VC 1.24. Original post: Hello there, the size prefixes in Volume Creation Wizard - Volume Size are misleading, because they don't follow the ISO standard from 2008 about byte prefixes (https://en.wikipedia.org/wiki/Binary_prefix) to better distinguish between binary and decimal prefixes. This may lead to getting containers larger than they should be, what may get annoying trying to fill a multiple Terabytes large HDD with...

Hello there, the size prefixes in Volume Creation Wizard - Volume Size are misleading, because they don't follow the ISO standard from 2008 about byte prefixes (https://en.wikipedia.org/wiki/Binary_prefix) to better distinguish between binary and decimal prefixes. This may lead to getting containers larger than they should be, what may get annoying trying to fill a multiple Terabytes large HDD with a few very large containers. Recognizing this after some hours of formatting isn't really that pleasant....

Hello there, the size prefixes in Volume Creation Wizard - Volume Size are misleading, because they don't follow the ISO standard from 2008 about byte prefixes (https://en.wikipedia.org/wiki/Binary_prefix) to better distinguish between binary and decimal prefixes. This may lead to getting containers larger than they should be, what may get annoying trying to fill a multiple Terabytes large HDD with a few very large containers. Recognizing this after some hours of formatting isn't really that pleasant....

Oh my gosh, now I know what my problem is: I always start Keepass directly from Favorites Bar in Ubuntu so I can't see any terminal messages by Keepass. If I execute cmd://bash -c "veracrypt [...]; veracrypt [...]" mono is executing these commands one after another and each running veracrypt instance checks itself for admin privileges and shows the graphical admin password prompt. If I try executing cmd://sudo bash -c "veracrypt [...]; veracrypt [...]" mono tries to open bash with admin privileges...

No problem, thank you for attempting to help me! :) Maybe Dominik could look into this problem to identify the module, that is responsible for this issue. A fix could be really helpful for people who are otherwise tempted to use the following insecure "solution" for convenience: https://security.stackexchange.com/questions/178610/is-it-secure-to-mount-veracrypt-without-sudo-password-in-this-way Other solution could be of course to create an external script that additionally has the passwords stored...

And when you run it from KeePass it asks for multiple passwords? Yes cmd://bash -c "veracrypt [...]; veracrypt [...]" two admin password prompts cmd://bash -c sudo "veracrypt [...]; veracrypt [...]" not executing cmd://sudo bash -c "veracrypt [...]; veracrypt [...]" not executing cmd://bash -c "sudo veracrypt [...]; sudo veracrypt [...]" not executing Seems sudo is blacklisted from cmd parser.

The bash -c "veracrypt [...]; veracrypt [...]" line in a fresh terminal asks only once for admin password.

I don't know any perl, but with some googling I tried this: URL: cmd://perl /sudoscript.pl "veracrypt --mount [/path/to/container1] --password={REF:P@I:X} --fs-options=X-mount.mkdir=0700 [/path/to/mountpoint1]; veracrypt --mount [/path/to/container2] --password={REF:P@I:Y} --fs-options=X-mount.mkdir=0700 [/path/to/mountpoint2]" sudoscript.pl 1 2 3#!/usr/bin/env perl -w system($ARGV[0]); If I use this script from terminal, it prompts for only one admin password. From Keepass still two prompts. Edit:...