Documentation update: Installation problem solved
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
#52 Documentation update: Installation problem solved
Hi Mounir,
Firstly, thanks for taking continuing where TrueCrypt stopped.
Secondly, the issue (and solution) I found.
OS: Linux 64-bit
Installer: GUI and text.
Problem: Running "veracrypt" from the cli always returned "-su: /usr/bin/veracrypt: No such file or directory", no matter what I did in terms of cli parameters. Not even "-h" worked.
Reason: I installed as root while my umask was 077.
Work-around: Reinstall with umask 022.
Comment: I find it very strange that no-one has picked this up before, especially given what VeraCrypt does.
8-)
John
Thank you for reporting this.
Setting umask to 077 has many downsides and this is one of them. Basically, you are disallowing installing applications from root that can be used by others.
All Linux distributions set root umask to 022 (maybe Redhat is an exception). I think that's why no one reported this before.
Did you explicitly change umask to 077?
Anyway, I will see if I can change umask temporarily in the installer to 022 and then restore it back to its original value after the installation is finished. I'm not sure though if this is the correct way to do things. Maybe I can just show a warning to the user that its umask doesn't have the standard value.
Actually, there is already an explicit call to "umask 022" at the begining of the installer and so all subsequent calls should inherite this umask value, including the calls to sudo and equivalent.
I have done a test by setting root umask to 077 and launching the installer as root and VeraCrypt was installed correctly and it was running with no issue (done on CentOS and Ubuntu).
Can you please give more information about your configuration so I can reproduce the issue? (Linux distribution and other parameters related to umask configuration).
Thanks.
Hi,
I got this problem too. It happened on Kali Linux on virtual machine.
I uninstalled veracrypt and installed using a file for x64 architecture and it worked, I also checked the umask which was set to 022 the first time around, so it probably wasn't that. Uninstall veracrypt and make sure you intall the right file for the architecture