Skip to content
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

Open
jaromil opened this issue Feb 1, 2017 · 5 comments
Open

Tomb hardened userspace bundle #242

jaromil opened this issue Feb 1, 2017 · 5 comments
Labels
wish feature we wish someone would refine and implement

Comments

@jaromil
Copy link
Member

jaromil commented Feb 1, 2017

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.

@jaromil jaromil added the wish feature we wish someone would refine and implement label Feb 1, 2017
@parazyd
Copy link
Member

parazyd commented Feb 3, 2017

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

@jaromil
Copy link
Member Author

jaromil commented Feb 3, 2017

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 bootstrap-musl.sh as a name for such scripts all across subdirs implementing this.

@parazyd
Copy link
Member

parazyd commented Feb 3, 2017

Yes. Let's figure out gtk-tray and qt-tray so we find a common ground whenever you have time :)

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.

@parazyd
Copy link
Member

parazyd commented Feb 3, 2017

OK, just to leave notes. I have managed to link everything statically on my Gentoo system.

[x] pinentry-curses
[x] gpg2
[x] cryptsetup
[x] e2fsprogs
[x] kdf-keys

sudo should stay system-wide. qrencode I can try to figure out (libpng). steghide is C++ and doesn't like being compiled for static linking.

@jaromil
Copy link
Member Author

jaromil commented Feb 5, 2017

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wish feature we wish someone would refine and implement
Projects
None yet
Development

No branches or pull requests

2 participants