I'd like to install Zulucrypt, "a front end to cryptsetup. It makes it easy to use cryptsetup to manage encrypted volumes by providing a Qt based GUI and a simpler to use cli front end to cryptsetup".
Needed:
1. libmount-devel
2. libblkid-devel
3. Qt-devel
4. gcc
5. gcc-c++
6. cryptsetup-devel
7. cmake
In apt-get I do not find Qt-devel and gcc-c++.
Anybody can suggest which packages I should install to have those installed?
Anybody already succeded in installyn Zulucrypt in siduction?
Thanks.
apt-get install libqt4-dev g++
cryptsetup luksFormat <device>
e.g.:
cryptsetup luksFormat /dev/sdb2
or:
man cryptsetup
simpler than any frontend ...
If you use rpm-based howtos, you gotta translate package names. -devel translates to -dev mostly in debian.
greetz
devil
Thanks to all.
Seems all dependencies have been installed, when I type the first command listed by the instruction file for building Zulucrypt:
cmake -DCMAKE_INSTALL_PREFIX=/usr/ -DCMAKE_BUILD_TYPE=MINSIZEREL
I get:
Make Error at zuluCrypt-cli/CMakeLists.txt:16 (message):
ERROR: could not find sys/mount.h header file
What is "mount.h header file", and how can I make it available?
Thanks
I tried last night and got the same result. All packages that provide these header files are installed. I am clueless at the moment and have no time to look into it further.
greetz
devil
Quote from: "devil"I tried last night and got the same result. All packages that provide these header files are installed. I am clueless at the moment and have no time to look into it further.
greetz
devil
Does debian have a different manner for searching headers than other distros?
did u clone the git -> https://code.google.com/p/zulucrypt/source/checkout ,
I guess yes.
cd to it.
mkdir build && cd build
ccmake ../ #(than press <c> to configure cmake, than <g> to generate)
cmake ../
make
su ...
make install
To uninstall it just type
make uninstall
as root in the build dirctory
thats works for me
edit, maybe you have to install cmake-curses-gui for ccmake
No, we used a tarball.
greetz
devil
mh, well
if u create a build directory after u expand the tarball und try the same steps as i posted above, i think it is also working fine.
But why not clone the git?
Because i wanted to try what the thread-starter did.
greetz
devil
It needs a little change in the sources for successfull building:
--- zulucrypt-4.6.1.orig/zuluCrypt-cli/CMakeLists.txt
+++ zulucrypt-4.6.1/zuluCrypt-cli/CMakeLists.txt
@@ -10,7 +10,7 @@
message( STATUS "Found mntent.h : " ${mntent} )
- find_file ( mount_sys sys/mount.h )
+ find_file ( mount_sys ${LIB_SUFFIX}/sys/mount.h )
if(NOT mount_sys)
message (FATAL_ERROR "ERROR: could not find sys/mount.h header file")
Then you can do
mkdir build && cd build
cmake . -DCMAKE_INSTALL_PREFIX=/usr/ \
-DLIB_SUFFIX=/$(DEB_HOST_MULTIARCH) \
-DCMAKE_BUILD_TYPE=MINSIZEREL
make
Btw, i have uploaded zulucrypt to our experimental repo.
Quote
Btw, i have uploaded zulucrypt to our experimental repo.
If anyone tries this, give feedback please.
If it works reliably, we might keep it .
greetz
devil
I installed it from repository.
It works if started as root. Started as normal user, it does not mount selected (encrypted) partition. I get messages like:
"Could not create mount point, invalid path or path already taken"
"Failed to open the volume, device may be already in use"
No matter in which folder I try to mount, included Home folder.
Partition mounted as root seem totally hidden when browsing as normal user.
Thanks
hallo everyone.
I am a developer of zuluCrypt.
I just googled "zuluCrypt" to see whats out there and this thread came up.
@towo
I use an rpm system and all header files are in "/usr/include".
Is it normal for this distro or debian distros to have header files in "lib/lib64" folders?
I will change the config files to reflect this if it is a standard location for header files.
Anything else particular in this distro i should tweak in my project?
@frapelli
Can you expand a little with your problem?
can you, for example, post the content of "zuluCrypt-test" command?
what version of zuluCrypt did you try?
you can know this by running "zuluCrypt-cli --version"
Thanks for trying zuluCrypt
Hi mhogomchungu
Sorry for delay, I lost hopes to get a solution, and did not check the thread for a while.
I retied Zulucrypt, and it seems to work now. Actually it create/mount partitions only as root, but it seems reasonable, and user car read/write after changing permission. I think the problem was that in my already encrypted partition there was a couple of file with names written in a sort of illegal character (kind of question mark) that prevented changing permissions for the whole partition. I deleted that file, could at last change permissions, and now I can read/write also as user.
I am using ZC version 4.5.0, installed from siduction repository (experimental).
I marked "SOLVED" this thread, although there is still, maybe, the issue about installing ZC on other Sid distros (maybe also Debian distros?)
Output of zuluCrypt-test seems OK, as far as I can understand.
Thank for your help, and thanks for Zulucrypt. I really missed it before you and maybe other developers created it.
root@siductionbox:/home/francesco# zuluCrypt-test
****************************
start test
****************************
creating mount point "/tmp/testing of volumes"
creating a plain file "/tmp/testing plain"
creating a luks file "/tmp/testing luks"
creating a plain volume
SUCCESS: volume created successfully
opening "/tmp/testing plain" volume using passphrase
SUCCESS: Volume opened successfully
closing "/tmp/testing plain" volume
SUCCESS: volume closed successfully
opening "/tmp/testing plain" volume using keyfile
SUCCESS: Volume opened successfully
closing "/tmp/testing plain" volume
SUCCESS: volume closed successfully
creating a luks volume
SUCCESS: volume created successfully
creating a backup of the volume luks header is strongly adviced.
Please read documentation on why this is important
opening "/tmp/testing luks" volume using passphrase
SUCCESS: Volume opened successfully
closing "/tmp/testing luks" volume
SUCCESS: volume closed successfully
opening "/tmp/testing luks" volume using keyfile
SUCCESS: Volume opened successfully
closing "/tmp/testing luks"
SUCCESS: volume closed successfully
check keys slots in use
30000000
add key to luks volume using passphrase and passphrase
SUCCESS: key added successfully
add key to luks volume using keyfile and keyfile
SUCCESS: key added successfully
add key to luks volume using passphrase and keyfile
SUCCESS: key added successfully
add key to luks volume using keyfile and passphrase
SUCCESS: key added successfully
check keys slots in use
11111000
remove added key using a passphrase
SUCCESS: key removed successfully
remove added key using a keyfile
SUCCESS: key removed successfully
check keys slots in use
01011000
deleting testing files
deleting mount point "/tmp/testing of volumes"
check to see if there are any undeleted zuluCrypt-xxx mappers
all mappers are deleted, good
****************************
end test
****************************
Quote from: "frapelli"Hi mhogomchungu
Sorry for delay, I lost hopes to get a solution, and did not check the thread for a while.
I retied Zulucrypt, and it seems to work now. Actually it create/mount partitions only as root, but it seems reasonable, and user car read/write after changing permission.
You took so long to respond,i,too,stop checking for your respond and i did not get/notice your response notification email for some reason.I just remembered this thread and came back to it to see if there are any responces.
It should be possible to create and open volumes from normal user accounts.If you are not able to do so then you are hitting a bug somewhere.
version 4.5.0 is too old now and whatever problem it may have,they are probably solved in the latest version.
I now do tests on pclinuxos,ubuntu,opensuse and fedora so things should also work on other debian systems too,the build issue reported in this thread should now be gone.
The current version is 4.6.2.This version has support for management of truecrypt volumes too and hence its a perfect substitute for truecrypt GUI application if you also have truecrypt volumes.
If you guys want a "one stop solution" for CLI and GUI based management of cryptsetup and truecrypt encrypted containers then zuluCrypt is your answer.
It also now ships with an additional tool called "zuluMount",it is a front end to zuluCrypt and its purpose is "to be used as a general purpose tool that mount and unmount zuluCrypt supported encrypted volumes as well as unencrypted volumes and it can be used as a substitute to udisks,pmount and related tools."
I will also ask/recommend an update to the recent version as version 4.5.0 is just too old.
The project page for more info is located at: http://code.google.com/p/zulucrypt/