Reinstalling Sanity

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
There is a slackbuild, which maybe fixes all this stuff, but itself has some odd dependencies.  The site has an installer for the cl version.

======Truecrypt binary root privileges======

The Truecrypt binary needs to have root privileges. I installed Truecrypt 6.0a on Slackware 12.1 and it gives me the same message. The fix is to create a group with the privilege of running the truecrypt binary and add your unprivileged (non-root) users to the truecrypt group so they can run Truecrypt. Do the following (as root):

<code>
# groupadd truecrypt
</code>

Now you edit the sudoers file (must be done with vi!)

<code>
# visudo
</code>

Add the following 2 lines to the bottom of the sudoers file:

<code>
# Allow users of truecrypt group to run truecrypt as root.
%truecrypt ALL=(root) NOPASSWD:/usr/bin/truecrypt
</code>

Save it and exit visudo
Now add your regular users to the truecrypt group

<code>
# gpasswd -a regularuser truecrypt
</code>

or for many users

<code>
# gpasswd -M first_user,second_user,etc truecrypt
</code>

Affected users need to log out and back in again.

The Truecrypt file containers default mount on:

<code>
/media/truecryptX
</code>

where X is the slot number you choose from the graphical interface when you mount the file container.

Mount and unmount with

<code>
truecrypt /path/to/encrypted/file /path/to/mount/point
truecrypt -d /path/to/mount/point
truecrypt -d # unmounts all
</code>

although mounting in non-default locations [[http://lyuts.net/blog/2011/10/device-busy-then-unmounting-truecrypt-container|seems to cause some serious difficulties (device busy) with unmounting]], so I suggest sticking with the default (in /media) unless there's a compelling reason not to.

https://wiki.archlinux.org/index.php/TrueCrypt#Mount_volumes_as_a_normal_user