-
Notifications
You must be signed in to change notification settings - Fork 271
Portable gocryptfs #79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes, no problem. Compile using "./build-without-openssl.bash". The
resulting "gocryptfs" binary has no dependencies and runs on any 64-bit
linux computer.
|
It would be great if stupidgcm was its own pkg that we could use in other projects. |
@Gaillard Thinking about it. Just out of interest, what project do you have in mind? |
Actually with the pending patch here golang/go#18498 I probably wouldn't end up using it. But if that doesn't go through, the small patch for stupidgcm would be preferable to the heavier spacemonkey's openssl. |
This makes it easier to use the package in external projects. See #79
Hmm, given that even spacemonkey-openssl does not get used much I guess stupidgcm would not fare much better. Probably the only user besides gocryptfs will be you, until the ARM64 assembly is merged ;) I think it makes more sense if you just copy the "stupidgcm" folder into your project. I have just dropped the only dependency it had (a659657). |
BTW I created stupidgcm because spacemonkey-openssl added a 0.5-seconds startup delay. I don't know if that has changed by now. |
Much appreciated thanks :) |
I would like to add some files encrypted with gocryptfs to a pendrive and keep a portable installation of gocryptfs to make it easy to decrypt those files in a non-previously set computer.
I couldn't find instructions about it. Is it possible?
The text was updated successfully, but these errors were encountered: