-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
Tomb hardened userspace bundle #242
Comments
Do you only have kdf-keys in mind or more? Perhaps my last two commits can give you some insight: https://github.com/parazyd/Tomb/commits/master |
Well done with that commit! I do have in mind an easy way to build all dependencies to the maximum possible extent. I suggest we keep |
I misunderstood your commend. Indeed yes, it is quite possible to have a static cryptsetup and such. I already have most of the workflow ready for coffin. One thing you can forget about is gtk/qt though. Those will not be possible to statically link. pinentry-curses is not a problem. |
OK, just to leave notes. I have managed to link everything statically on my Gentoo system. [x] pinentry-curses
|
ACK, Good job! Pity for steghide, I shall have a look into it sometimes. Qrencode is not so important as its only for exporting keys to backup them. I hope is easy to isolate the build procedure into an extras/ subdir? |
It would be nice to have a build environment for a static build of Tomb's userspace tools, for instance using musl-libc for all dependencies. It could be a set of script in extras that build this and we may distribute pre-compiled binaries for x86.
The text was updated successfully, but these errors were encountered: