You are not logged in.
Pages: 1
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.
Offline
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.
Offline
Hi Rantanplan, Shann,
Sorry for beeing unexact in my description. Indeed i work with SliTaz Current64.
So, shann, I would appreciate Your check.
Offline
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 you
Offline
Please find attached the recipes for veracrypt and the required packages suitable for SliTaz current64.
Offline
There is also a recipe for localised messages for veracrypt.
Offline
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).
[attachment=53266,3735]
Offline
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.
Offline
The veracrypt error message is somewhat misleading. What is meant is:
[c]failed to execute sudo command[/c]
When 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:
[c]%wheel ALL=(ALL:ALL) ALL[/c]
- add unprivileged user to group [c]wheel[/c]
Offline
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 
[attachment=53269,3736]
Offline
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 [c]tazpkg up -r[/c] could be purpose to upgrade veracrypt to 1.26.24
Offline
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!
Offline
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
Offline
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.
Offline
Hi HDS,
No problem, you're welcome.
I leave package as it 
I know we miss few thinks for more smooth experience, for example printer support, don't have tool for purpose find and install driver. For android device i add rules on udev but need to recheck, if remind i don't add libmtp, gvfs-libmtp on iso, in case not plug and play.
If you see miss think, don't hesitate.
Offline
Hi Shann,
we worked successfully with an office-PC (include veracrypt) on base of Slitaz-current64 for some month now.
Doing an (first) actualization some day before goes well with the exception of veracrypt (s. screenshot).
The reason for the occured problem is the installation of dmsetup and libdevmapper in version 2.03.15 in the course of veracrypt installaion. (Verified by an Virtualbox-VM on base of slitaz-current64-core64-grub2.iso, application of all updates with a following veracrypt-installation).
Installation of dmsetup and libdevmapper in version 2.03.31 solves the problem.
Personal history
I had these packages already on the Slitaz-PC before the installation of the official veracrypt-package due to the help of HGT mentioned in some post in the past. Since I have not blocked the packages against Update I ran into the problem.
[attachment=53857,3831]
Offline
Hi HDS,
Sad sorry to break veracrypt
.
For updates purpose, think related to mass rebuild when switched to fs.tar.xz in October.
I bump lvm2 and other packages related (libvdevmapper, dmsetup) to 2.03.38.
Doing test on qemu with iso and veracrypt / dmsetup 2.03.15, same issue of dm_udev_create_cookie.
After update dmsetup, libdevmapper to 2.03.38, mount device work as expected.
Repository updated with lvm2,dmsetup,libdevmapper (2.03.38).
Also updated Qt5 to 5.15.18, vlc 3.0.23 and rebuild wireshark, virtualbox (link with new qt5).
Offline
Hi Shann,
thank your very much for your quick response. The update works fine for me!
Offline
Pages: 1
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]