TrueCrypt: socket not connected /tmp/.truecrypt_aux_mnt1/control

Issues & Assistance
1

Hi,

after running the TrueCrypt 7.2 installation script and additionally installing gtk2 (wasn’t installed as dependency…) I can launch the app, but trying to mount a drive I am getting

socket not connected /tmp/.truecrypt_aux_mnt1/control

mount shows:

truecrypt on /tmp/.truecrypt_aux_mnt1 type fuse.truecrypt (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
truecrypt on /tmp/.truecrypt_aux_mnt2 type fuse.truecrypt (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
truecrypt on /tmp/.truecrypt_aux_mnt3 type fuse.truecrypt (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)

After googling for a while, it seems that there is an incompatibility between (the old) TC and (the new) fuse version which could be solved either by
a) downgrading fuse or
b) rebuilding TC from source

I don’t want (a) and have failed with (b).

Unfortunately, veracrypt is no longer an alternative since it has stopped to support TC containers or drives.

Any more ideas anyone?

Tx,

T.

2

Why not use luks encryption ? It is linux native and works very well .
I may be too suspicious but I don’t trust truecrypt/veracrypt/bitlocker/etc. that come from big corporation. :face_with_raised_eyebrow:

3

Could you help to understand why this problem occurs only in CachyOS and in none of my other distros (OpenSUSE, LMDE, LM, MX, Q4OS)? Has CachyOS applied any mods to fuse or ntfs that aren’t present in other distros?

I would be happy to provide more debugging info, as required.

I notice that truecrypt is no longer available from the repos used by octopi/paru/pacman, so I used the installer from
https://github.com/DrWhax/truecrypt-archive/blob/master/TrueCrypt-7.2-Linux-x64.tar.gz

and I tried to compile the source
https://github.com/DrWhax/truecrypt-archive/blob/master/TrueCrypt-7.2-source-unix.tar.gz

Best,

T.

4

If you can open it in other distros, open it there and transfer the data to a newer container type.

5

CachyOS-Settings/usr/lib/udev/rules.d/80-ntfs3-by-default.rules at master · CachyOS/CachyOS-Settings · GitHub is the only modification done for NTFS in CachyOS. Can you remove that file and check if it works?

6

Thank you for the proposal.
I’ve made a test but the error remains. :confused:

Best,

T.

7

Since I only need TC to mount (and unmount) already existing TC volumes or files, it seems I don’t need to install it at all.

Instead, I have found the following workaround:

Mount script:

#!/usr/bin/env bash
DIR="/media/truecrypt1"
MAP="truecrypt1"
DEV="sdc"
if mount | grep $DIR > /dev/null; then
    echo "$DIR is already mounted; nothing to do."
else
    sudo cryptsetup --type tcrypt open /dev/$DEV $MAP
    if [ ! -d $DIR ]; then
        sudo mkdir -p $DIR
    fi
    sudo mount -o uid=1000 /dev/mapper/$MAP $DIR/
    echo "$DIR was mounted."
fi

Note: instead of –type tcrypt open you can also use tcryptOpen

Unmount script:

#!/usr/bin/env bash
DIR="/media/truecrypt1"
MAP="truecrypt1"
if mount | grep $DIR > /dev/null; then
    sudo umount -l $DIR
    sleep 0.5
    sudo dmsetup remove $MAP
    sleep 0.5
    sudo cryptsetup close $MAP
else
    echo "$DIR is not mounted; quitting."
fi
sudo rmdir $DIR >/dev/null

Using python’s pystray, these scripts can even be put “behind” an icon in the systray.

I am closing the problem with my solution.

Best,

T.