I switched a Office-Windows-10-PC to SliTaz64.
With a lot of help from a friend this works.
Especially he made a veracypt-package (and referenced packages libdevmapper, lvm2, dmsetup) for SliTaz64 since there is no such package in the official repository.
For Update-Reasons I would appreciate an official package here.
veracrypt
(16 posts) (4 voices)-
Posted 1 month ago #
-
Hello,
at the bottom of this screen click on "Packages" and type "veracrypt" in the field.
But, may be, i have not understand your request.
Bests regards.
Posted 1 month ago # -
Hi HDS, Rantanplan
HDS, you said SliTaz64, SliTaz Current64 ?
In that case infact, i don't package veracrypt but available on cooking.Let's me check to build it.
Posted 1 month ago # -
Hi Rantanplan, Shann,
Sorry for beeing unexact in my description. Indeed i work with SliTaz Current64.
So, shann, I would appreciate Your check.Posted 1 month ago # -
Hi HDS,
Ok thanks for confirmation.
I try to build veracrypt 1.25.9 and also 1.26.24.
When try to test create device and mount it, seem issue about "broken pipe" and see "VeraCrypt::File::Write:395"On your side it's work without issue ?
Can you please put this file in attachment "/var/lib/tazpkg/installed/veracrypt/receipt" ? Thanks
Maybe i miss think, i test on qemu, and install also lvm2 to ensure i have same packages as youPosted 1 month ago # -
Please find attached the recipes for veracrypt and the required packages suitable for SliTaz current64.
Posted 1 month ago # -
There is also a recipe for localised messages for veracrypt.
Posted 1 month ago # -
Hi HGT,
Thanks for receipts, i check it's same, first i build veracrypt 1.25.9 (same receipt as cooking), and bump to 1.26.24.
For both i have this error when i try to mount disk create as FAT or other ext (create successfully without issue).
Posted 1 month ago # -
Bonjour @Shann,
question de Candide :
cette erreur pourrait-elle due à un user ou similaire ?Mais, probablement, as-tu déjà vérifié.
Avec truecrypt, il fallait désactiver "do not use kernel cryptographic service" : ce paramètre est ausi présent dans veracrypt 1.25, mais je ne sais pas s'il existe toujours dans la version 1.26.x
J'espère ne pas générer du bruit inutilement.
Amitiés.
Posted 1 month ago # -
The veracrypt error message is somewhat misleading. What is meant is:
failed to execute sudo commandWhen not run by the system administrator (root), verycrypt uses sudo for mounting volumes.
So do as follows:
- install package sudo
- insert for example (using visudo) in sudoers file:
%wheel ALL=(ALL:ALL) ALL- add unprivileged user to group
wheelPosted 1 month ago # -
Bonjour Rantanplan,
Non je n'avais pas essayer, l'option est toujours présente avec veracrypt 1.26.x, malgré cela pas de changement.
Hi HGT,
Thanks, i try after install sudo and adjust sudoers file and add user to wheel group.
Now it's work perfectly, thanks for tips, message not really clear and with verbose mode i don't have detail about sudo missing/misconfig.Need to adjust veracrypt receipt to add sudo as depend and message at post install :)
Posted 1 month ago # -
I adjust veracrypt receipt to add required runtime deps (sudo, dmsetup, libdevmapper and linux64-md)
Also add sudoers file for run veracrypt with privilege if member of veracrypt group (post-message to inform user add it to group)I push packages on my space, it's available for slitaz Current64, if you run
tazpkg up -rcould be purpose to upgrade veracrypt to 1.26.24Posted 1 month ago # -
Thanks, Shann.
Installation works fine. But the added sudoers-file veracrypt in /etc/sudoers.d allows only root the execution of veracrypt. Therefore i got a root-password-request for any group-member of veracrypt except root.
I changed the the content of the suoers-file into:
%veracrypt ALL=(ALL:ALL) NOPASSWD : /usr/bin/veracrypt
Now everythings works well.
Thanks again!Posted 1 month ago # -
Hi HDS,
Strange, when i test on live to recheck all that work i don't see issue with sudoers.
I add user to veracrypt group, logout and mount successfully device ask password for encrypt device znd password for user to mount.Of course i can adjust sudoers file to no ask password to be more smooth experience
Posted 1 month ago # -
Hi Shann,
in the meantime I learned from HGT that my expectation for veracrypt-usage was coined by my windows-experience: In windows there is no request for user password when mounting an encrypted device!
In SliTaz (without the mentioned manipulation of sudoers) a member of the group veracrypt is asked for "Administrator-Passwort" when mounting an encrypted device. Thats seems to be a misleading translation to german from the original text which was translated by me to "root-password-request".
Asking for the user-password is in some sense a "second factor authentication" and by that a usefull feature.
So please leave your veracrypt-package as it is.
Sorry for the misunderstanding and many thanks for your quick and compentent work on the subject.Posted 1 month ago #
Reply »
You must log in to post.