hardcoresushi
/
libgocryptfs
1
0
Fork 0
Code Issues Pull Requests Releases Activity
Re-design of the original gocryptfs code to work as a library.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1,972 Commits
2 Branches
0 Tags
6.0 MiB
Go 93.7%
C 4.3%
Shell 1.7%
Makefile 0.3%
 
 
 
 
libgocryptfs
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9e98192442'
${ noResults }
Go to file
Hardcore Sushi 9e98192442
Fix race condition when registering files 		1 year ago
allocator Genesis patch 2 years ago
internal Allow the password hash to be returned when creating a volume 1 year ago
.gitignore Genesis patch 2 years ago
LICENSE LICENSE: add full name 7 years ago
README.md Thread safety 1 year ago
build.sh Better build script 1 year ago
common_ops.go Thread safety 1 year ago
dircache.go Thread safety 1 year ago
directory.go Thread safety 1 year ago
file.go Fix race condition when registering files 1 year ago
go.mod Allow the password hash to be returned when creating a volume 1 year ago
go.sum Allow the password hash to be returned when creating a volume 1 year ago
helpers.go Update FUSE related stuff according to gocryptfs fusefrontend 1 year ago
main.go libgocryptfs: update to gocryptfs v2.2.0 2 years ago
volume.go Fix race condition when registering files 1 year ago

README.md

libgocryptfs is a re-desing of the original gocryptfs code to work as a library. Volumes are not mounted with FUSE but rather opened in memory and accessed through API calls. What the purpose ?

  • Allow the use of gocryptfs in embedded devices where FUSE is not available (such as Android)
  • Reduce attack surface by restricting volumes access to only one process rather than one user

Warning !

The only goal of this library is to be integrated in DroidFS. It's not actually ready for other usages. libgocryptfs doesn't implement all features provided by gocryptfs like symbolic links, editing attributes, creating reverse volume... Use it at your own risk !