Crates.io | encryptedfs |
lib.rs | encryptedfs |
version | 0.1.27 |
source | src |
created_at | 2024-04-21 11:10:36.217029 |
updated_at | 2024-04-25 13:15:37.241229 |
description | [DEPRECATED] move to rencfs. An encrypted file system that mounts with FUSE on Linux. It can be used to create encrypted directories. |
homepage | |
repository | https://github.com/radumarias/encryptedfs |
max_upload_size | |
id | 1215301 |
size | 297,552 |
⚠️ Warning
Moved to rencfs. Please use that instead.
An encrypted file system that mounts with FUSE on Linux. It can be used to create encrypted directories.
It can then safely backup the encrypted folder on an untrusted server without worrying about the data being exposed.
You can also store it in any cloud storage like Google Drive, Dropbox, etc. and have it synced across multiple devices.
You can use it as a command line tool to mount an encrypted file system, or directly using the library to build your own binary (for library, you can follow the documentation).
To use the encrypted file system, you need to have FUSE installed on your system. You can install it by running the following command (or based on your distribution)
Arch
sudo pacman -Syu && sudo pacman -S fuse3
Ubuntu
sudo apt-get update && sudo apt-get -y install fuse3
You can install the encrypted file system binary using the following command
yay -Syu
yay -S encryptedfs
You can install the encrypted file system binary using the following command
cargo install encryptedfs
A basic example of how to use the encrypted file system is shown below
encryptedfs --mount-point MOUNT_POINT --data-dir DATA_DIR
Where MOUNT_POINT
is the directory where the encrypted file system will be mounted and DATA_DIR
is the directory where the encrypted data will be stored.
It will prompt you to enter a password to encrypt/decrypt the data.
The encryption key is stored in a file and encrypted with a key derived from the password. This offers the possibility to change the password without needing to decrypt and re-encrypt the whole data. This is done by decrypting the key with the old password and re-encrypting it with the new password.
To change the password, you can run the following command
encryptedfs --change-password --data-dir DATA_DIR
Where DATA_DIR
is the directory where the encrypted data is stored.
It will prompt you to enter the old password and then the new password.
You can specify the encryption algorithm and derive key hash rounds adding these arguments to the command line
--cipher CIPHER --derive-key-hash-rounds ROUNDS
Where CIPHER
is the encryption algorithm and ROUNDS
is the number of rounds to derive the key hash.
You can check the available ciphers with encryptedfs --help
.
Default values are ChaCha20
and 600_000
respectively.
You can specify the log level adding the --log-level
argument to the command line. Possible values: TRACE
, DEBUG
, INFO
(default), WARN
, ERROR
.
--log-level LEVEL
docker pull xorio42/encryptedfs
Start a container to set up mount in it
docker run -it --device /dev/fuse --cap-add SYS_ADMIN --security-opt apparmor:unconfined xorio42/encryptedfs:latest /bin/sh
In the container create mount and data directories
mkdir fsmnt && mkdir fsdata
Start encryptedfs
encryptedfs --mount-point fsmnt --data-dir fsdata
Enter a password for encryption.
Get the container ID
docker ps
In another terminal attach to running container with the above ID
docker exec -it <ID> /bin/sh
From here you can play with it by creating files in fsmnt
directory
cd fsmnt
mkdir 1
ls
echo "test" > 1/test
cat 1/test
git@github.com:radumarias/encryptedfs.git
To build from source, you need to have Rust installed, you can see more details on how to install it here.
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
Accordingly, it is customary for Rust developers to include this directory in their PATH
environment variable.
During installation rustup
will attempt to configure the PATH
. Because of differences between platforms, command shells,
and bugs in rustup
, the modifications to PATH
may not take effect until the console is restarted, or the user is logged out, or it may not succeed at all.
If, after installation, running rustc --version
in the console fails, this is the most likely reason.
In that case please add it to the PATH
manually.
Also these deps are required (or based on your distribution):
Arch
sudo pacman -Syu && sudo pacman -S openssl lib32-openssl fuse3 base-devel
Ubuntu
sudo apt-get update && sudo apt-get install libssl-dev openssl fuse3 build-essentials
cargo build
cargo build --release
cargo run -- --mount-point MOUNT_POINT --data-dir DATA_DIR