How to create an encrypted folder for my private files?

[malikawan]

How to load fuse module any idea please?

[Rich]

Hi malikawan

bcrypt is not present in tinycore 4.7.7. I am using tinycore 4.7.7

Sure it is. It's part of base and located in  /usr/bin/.

[tinypoodle]

in my opinion bcrypt has some security issues

Could you elaborate please?

one aspect of many others:
the debian packagers did not include the package in the actual stable branch yet, so i had to look for alternatives

1. How would that be related to security issues?
2. How would that be of any relevance to Core, where bcrypt is included in base since many years and a specific boot code "protect" is provided with a mechanism to encrypt backup and decrypt at boot time out of the box?
3. With "many others" we are just back to "could you elaborate?" again...   

[malikawan]

How to load fuse module any idea please?

[Juanito]

encfs will need to be recompiled against the tc-5.x boost extension in order to work in tc-5.x

[malikawan]

Thanx for reply Juanito

I am using tinycore 4.7.7 and encfs installed but the problem is fuse module how i load it ?

[Juanito]

In fact the fuse module is compiled into the kernel so there is no need to load it.

[malikawan]

But by default fuse module not loaded now what to do to load it

[Juanito]

When a module is compiled into the kernel you don't need to load it - it is there for use if required.

[malikawan]

How to solve these problems please any idea

fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
fuse failed.  Common problems:
 - fuse kernel module not installed (modprobe fuse)
 - invalid options -- see usage message

[malikawan]

How to solve these problems please any idea while using encfs extention

fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
fuse failed.  Common problems:
 - fuse kernel module not installed (modprobe fuse)
 - invalid options -- see usage message

[gerald_clark]

We can't tell you what is wrong when you don't show us the command you are running that produces that error.

[malikawan]

After giving that command

tc@box:~$ encfs ~/.atserial /home/tc/AT-SERIAL

[malikawan]

An easy approach would be to use the natively supported boot code "protect", in which case backup is encrypted and gets decrypted at boot.........................

i use boot code "protect" but it require password every time when boot

[netnomad]

hi malikawan,

i also use boot code "protect" and the required password substitutes my user password at every boot.
confidential files and data are stored in an encrypted file-container that is secured by an additional password and this file-container is only opened by request, when these encrypted files are really needed :-)

i use cryptsetup with a file-container that is mounted by a loop-device:

$DB is my mount-point
$DATABOX is my file-container

     sudo mkdir -p /mnt/$DB
     sudo mknod -m 660 /dev/loop256 b 7 256 > /dev/null 2>&1
     sudo losetup /dev/loop256 $DATABOX     > /dev/null 2>&1
     sudo cryptsetup luksOpen /dev/loop256 $DB
     sudo mount -t ext3 -o rw,defaults /dev/mapper/$DB /mnt/$DB

this solution can be used on different linux-platforms without any changes...