It looks like gocryptfs is going in the same direction as encfs. It’s been a year since the last update. Is it still maintained? What are some alternatives?
This might be the canonical source for the project: https://github.com/rfjakob/gocryptfs
Last commit was 4 hours ago.
Not sure what’s meant by ‘commit’, but the same github page shows the last release to be August, 2025.
‘Commit’ basically means the last change saved to the project. If there are still regular commits being made to the project, then it is pretty safe to say it is still active. You can see a list of commits here. Looks pretty active to me.
If you look at the release history, there was about a year and half between v2.4.0 and v2.5.0, so about a year since the last release seems pretty normal for the project.
1 Like
@jonc why do you think it would be updated? Unless there is a security or bug report, then it would be backported, version numbers are just a placeholder on Leap, what does the change log say?
1 Like
No particular reason. I guess knowing what happened to encfs makes me nervous.
It is version 2.6.1 in Tumbleweed, will still be the same version in Leap 16.1 as it was in Leap 16.0.
If you have concerns, then a bug report is likely needed…
I can confirm since the issues I reported hasn’t been solved.
You can break it simply by copying mixed UIDs into a dir.
Its very basic unimplemented fuse calls.
@dza zfs… good luck… 
The issue is the version on Leap 16.0, if can duplicate your issue on Leap 16.0 with a supported filesystem and the current installed version, then indeed a bug report is needed.