EncFS (http://www.arg0.net/encfs) is awesome. Security issues are fine for purposes needed but problem is file name limit (about 190). CryFS (https://www.cryfs.org/) solves file name limit and is great too (not to mention hides file names and directory structure). However have found that when browsing folders with lots of directories and files the performance can be difficult.

So want to give gocryptfs (https://nuetzlich.net/gocryptfs/) a try and test speed. It's probably a little less secure than CryFS but faster. No package available for distribution so followed instructions here to install: https://nuetzlich.net/gocryptfs/quickstart/

Got stuck at "Download the corresponding binary and extract the archive into /bin." Downloaded gocryptfs_v1.2.1_debian8_amd64.tar.gz and extracted to /bin but running

doesn't print the string like instructions says it will on success. Am I missing something (running some kind of bash file?) to install gocryptfs?

Hi schnappi.

It is ~/bin (i.e. the bin directory in your home directory) that you want to be extracting the archive to, not /bin.

See if that makes a difference.

Extracted the files to /home/bin but still not having any luck. Feel like am totally missing something.

There are probably other issues to resolve as well, but it shouldn't be /home/bin either, it should be ~/bin, which equates to e.g. /home/schnappi/bin, replacing schnappi with whatever your username is.

Which distro (and version) are you running? 32-bit or 64-bit?

/home/user/bin is what was meant. It's a Ubuntu 16.04 32-bit server and the package is only available in repository for 17.04. Might just reach out to gocryptfs on GitHub or compile from source (first time ever that compiling from source is the easier way to install something).

Just for info, the 17.04 deb installs correctly on my Mint 18.1 system (equivalent of 16.04).

However, running gocryptfs -version only returns gocryptfs with no version info. I assume that this is what you have been experiencing as well.

Figured it out.

&
or

Can't just run "gocryptfs" alone (or any script) from current directory.

That's probably because the current directory isn't in $PATH for the session or script.

Even if installed in ~/bin as suggested by hydrurga, it is unlikely that directory would be in $PATH either by default.
Of course, it could always be added...

1 members found this post helpful.

@scasey How can one set the "$path" for any given session or script so one doesn't need to use "./"? Just wondering.