Package Details: zulucrypt 6.2.0-1

Git Clone URL: https://aur.archlinux.org/zulucrypt.git (read-only, click to copy)
Package Base: zulucrypt
Description: A cli and gui frontend to cryptsetup
Upstream URL: https://mhogomchungu.github.io/zuluCrypt
Keywords: cryptsetup encryption security tcplay truecrypt veracrypt
Licenses: GPL
Conflicts: zulucrypt-git
Submitter: salan54
Maintainer: salan54
Last Packager: salan54
Votes: 70
Popularity: 0.038126
First Submitted: 2013-02-03 13:05 (UTC)
Last Updated: 2022-06-20 15:38 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 13 Next › Last »

egrupled commented on 2017-07-10 09:21 (UTC) (edited on 2017-07-10 09:22 (UTC) by egrupled)

There is typo in new PKGBUILD: -D5CMAKE_BUILD_TYPE=release should be: -DCMAKE_BUILD_TYPE=release

egrupled commented on 2017-07-06 21:29 (UTC)

@salan54 That's reasonable. Thanks.

salan54 commented on 2017-07-06 18:45 (UTC)

@egrupled : this is the conversation I had with the developer about KDE and Gnome flags : "I looked at the PKGBUILD file this morning before the request was made and i though the same too,that the option should be "NOKDE=false" if present but it should be removed all together. I think both NOGNOME and NOKDE options should not be present in the PKGBUILD file. This way, support for libsecret and kde wallet will be auto enabled when they are found to be present and disabled when they are found to be absent. Just don't mention kwallet in a list of dependencies to avoid dragging it in as a forced dependency but libsecret forced dependency should stay since it doesnt drag in that much. This way,those who want KDE integration can install kwallet first and then build zuluCrypt and zuluCrypt will pick it up automatically." I will remove the KDE and Gnome flags from the PKGBUILD. Of course, you can always edit the PKGBUILD to fulfil your needs.

egrupled commented on 2017-07-06 11:54 (UTC) (edited on 2017-07-10 09:24 (UTC) by egrupled)

@salan54 Could you enable kwallet support by changing -DNOKDE=true to -DNOKDE=false?

salan54 commented on 2017-07-06 08:29 (UTC)

version 5.2.0 -- add ability to select a file manager to use to open mount points. A file manager can be set through zuluCrypt-gui->menu->options->set file manager. -- dont run zuluCrypt-gui and zuluMount-gui from root's account when running in mixed mode. -- add arabic translation.

salan54 commented on 2017-07-05 21:04 (UTC)

@FabioLolix : yes i know, zuluCrypt was updated this morning to version 5.2.0 I will update the package asap. Please be patient ;-)

mhogomchungu commented on 2017-05-17 17:31 (UTC)

@salan54 SiriKali[1] maintainer managed to add the signature verification step and looking at how they did it may help you in trying to add the ability here. [1] https://aur.archlinux.org/packages/sirikali/

egrupled commented on 2017-05-17 17:20 (UTC)

@salan54 I have no idea, can't reproduce this. You can try to delete or rename ~/.gnupg folder and start from fresh config. @mhogomchungu Archlinux is already pushing gpg checks whenever possible[1] so using it in AUR would be consistent. Also if you sign your releases (which is great) you can expect that someone actually verifies them :) Anyway I thought it would be a nice feature for this PKGBUILD as zulucrypt targets people interested in additional security. Of course I'm not pushing anyone to this especially if our maintainer have issues. [1]https://www.archlinux.org/todo/use-gpg-signatures-and-https-sources/

mhogomchungu commented on 2017-05-17 09:12 (UTC)

In my opinion,this checking of signature adds more security and also adds more inconvenience and i think if it is to be implemented,then it should be off by default. checking of a hash should be enough to be sure the package is authentic.

salan54 commented on 2017-05-17 09:00 (UTC)

@egrupled : Sorry for the delay but I'm quite busy these days... Anyway, that's what I got (As you can see, I already checked Francis' public key) : [alain@rdc2010 zulucrypt]$ LC_ALL=C gpg --recv-keys 3AD67A14194FE8E7AEFCA19C3E1F380427A5D3CA gpg: key 3E1F380427A5D3CA: "Francis Banyikwa <mhogomchungu@gmail.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 [alain@rdc2010 zulucrypt]$ LC_ALL=C makepkg ==> Making package: zulucrypt 5.1.0-2 (Wed May 17 10:54:39 CEST 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found zuluCrypt-5.1.0.tar.bz2 -> Found zuluCrypt-5.1.0.tar.bz2.asc ==> Validating source files with md5sums... zuluCrypt-5.1.0.tar.bz2 ... Passed zuluCrypt-5.1.0.tar.bz2.asc ... Skipped ==> Validating source files with sha256sums... zuluCrypt-5.1.0.tar.bz2 ... Passed zuluCrypt-5.1.0.tar.bz2.asc ... Skipped ==> Verifying source file signatures with gpg... zuluCrypt-5.1.0.tar.bz2 ... FAILED (invalid public key 3AD67A14194FE8E7AEFCA19C3E1F380427A5D3CA) ==> ERROR: One or more PGP signatures could not be verified! I hesitate to implement pgp check in the package from fear that users face these problems... Any idea ?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 13 Next › Last »