Cryptomator for Raspberry Pi

anon24105312 · February 3, 2022, 10:05pm

I’ve been testing this on a Pi4, with 2 operating systems. RaspberrypiOS 64bit (manually built) and Arch linux using the AUR repository script.

in both cases vaults can be created and unlocked using webdav, but “revealing the vault” in FUSE gives an input/output error.

I have tried with the default unlock path, and also by making an empty folder in home, then specifying the unlock location. no files are shown in the folder when browsing to it manually in a file manager.

Using “ls” on the parent dir, the locked and unlocked folders shows as

drwxr-xr-x 3 pi pi 4096 Feb 3 21:48 asdf
d??? ? ? ? ? ? asdfunlocked

NOTE
I’ve also had FUSE issues with cryptomator-cli on armhf and arm64 ,but they work fine on x64. - Wondering if there is an issue with the fuse adapter working on ARM?

github.com/cryptomator/cli

Mounting via FUSE on Raspberry PI 4 (raspbianOS/debian) show all files as 0 bytes

opened 12:37PM - 14 Nov 20 UTC

amigagamer

Thank you for the addition of Fuse , it is working great on my x86/Mint desktop…. However when I mount my vault on Raspberry pi (debian buster on ARM) with the same settings all files in the vault show as 0 bytes. Steps to reproduce: I mount my cloud provider with Rclone. `rclone mount CloudProvider: ~/Cloudprovider --vfs-cache-mode writes ` I then mount my vault with `java -jar cryptomator-cli --vault CloudVault=~/CloudProvider/CloudVault --fusemount CloudVault=~/CloudVaultMount` The vault unlocks and is browseable, but individual files show as 0 bytes and will not open. Edit : additional info - 1. Mounting with Webdav works fine, all files show correct sizes and are readable. 2. The maven compile was performed on the PI, copying the JAR over to the Mint 20 x86 machine is working fine.