New version of VeraCrypt 1.17, (TrueCrypt fork). It's not easy to install without CCM (Centre de Contrôle Mageia) ! (impossible for me, and many people...). Thank you ! Hodos Reproducible: Steps to Reproduce:
Assigning this package request to packagers collectively. On the voluntary basis, one of them might want to package and maintain this piece of software.
Version: 1 => CauldronAssignee: bugsquad => pkg-bugs
I've got a package lying around locally which I'm testing, called zulucrypt, which offers TrueCrypt, LUKS and VeraCrypt support, among others: https://mhogomchungu.github.io/zuluCrypt/ For TrueCrypt support it brings along a bundled copy of tcplay: https://wiki.archlinux.org/index.php/Tcplay which is basically a TrueCrypt reimplemantation. zulucrypt also supports opening VeraCrypt volumes. Would that also suffice, or do you explicitly need VeraCrypt ?
Status: NEW => ASSIGNEDCC: (none) => doktor5000Assignee: pkg-bugs => doktor5000
Florian, I need explicitly and only VeraCrypt. I think that if you or somebody else packs VeraCrypt for "CCM" Mageia, a lot of people will be happy. VeraCrypt seems a solution safe to replace TrueCrypt.Thank you.
Summary: High Security Disk Encryption VeraCrypt is a free disk encryption software brought to you by IDRIX and that is based on TrueCrypt 7.1a. => package request: veracrypt - a free disk encryption software based on TrueCrypt 7.1a
Well, on linux both veracrypt and zulucrypt are just frontends to dm-crypt, and basically both provide the same support for veracrypt volumes. So adding both doesn't make much sense to me, when one project offers more functionality and seems maintained better. See e.g. https://bbs.archlinux.org/viewtopic.php?pid=1566011#p1566011 I've got a package for veracrypt, but it seems to be problematic. Upstream seems to recommend building with a static/bundled versions of wxgtk (same for the official veracrypt packages) which is disregarded for maintenance and security reasons. If we update wxgtk, it's not ensured that veracrypt will also offer a timely update for the bundled version. Also veracrypt in general seems to focus more on windows systems, from what I read. And when using the veracrypt package on current cauldron, there are quite a few issues with the GUI, seems it's not made to be used with gtk3.
just found this thread while looking for bug reports with wxgtk+gtk3 problems similar to this one: https://bugs.mageia.org/show_bug.cgi?id=17956 which is the same as this: https://bugs.launchpad.net/kicad/+bug/1461698 I didn't try the veracrypt gui mentioned by Florian, but it may very well be that there too, the problems are not in the program gui but one of the many bugs in wxgtk that only occurs when wxgtk is built against gtk3 (as is the case in Mageia), as opposed to GTK2 which is the default in the wxgtk built settings. The strong message of the second link above is: only build wxgtk against gtk2, not gtk3, or you get that kind of display/refresh/gui problems
CC: (none) => c934w-xavm493b
As mentioned in bug 17956 veracrypt also seems to require wxgtk3.0, see: Compiling Application.cpp In file included from GraphicUserInterface.h:20:0, from Application.cpp:19: Forms/WaitDialog.h:15:32: fatal error: wx-3.0/wx/msgqueue.h: No such file or directory compilation terminated.
(In reply to Florian Hubold from comment #6) > As mentioned in bug 17956 veracrypt also seems to require wxgtk3.0, see: > > Compiling Application.cpp > In file included from GraphicUserInterface.h:20:0, > from Application.cpp:19: > Forms/WaitDialog.h:15:32: fatal error: wx-3.0/wx/msgqueue.h: No such file or > directory > compilation terminated. I think that means that it requires wxGtk 3.0, but not necessarily the GTK+3 flavour, wxGtk 3.0 can still be built against GTK+2 (this collision between version numbers of wxGtk and GTK+ itself lead to very weird package names by Fedora :P).
(In reply to Rémi Verschelde from comment #7) > I think that means that it requires wxGtk 3.0, but not necessarily the GTK+3 > flavour, wxGtk 3.0 can still be built against GTK+2 Yeah was a little lazy hinting at bug 17956, especially at the last comment, where that was discussed. And even if it can be built against gtk2, seems we won't do that AFAIU due to horrible security issues with old webkit it would also link against.
Hello, I have created a functional package for Mageia 6. Here is the contents of the .spec. %define debug_package %{nil} Summary: Disk encryption software Name: veracrypt Version: 1.19 Release: 1 License: Apache License 2.0 Group: File tools Url: https://veracrypt.codeplex.com Source0: https://github.com/veracrypt/VeraCrypt/archive/VeraCrypt-VeraCrypt_%{version}.tar.gz Patch1: veracrypt-1.0f-2-no-makeself.patch Patch2: veracrypt-1.0f-2-desktop.patch BuildRequires: wxgtku3.0-devel BuildRequires: nasm BuildRequires: fuse-devel BuildRequires: imagemagick %description Free disk encryption software based on TrueCrypt. %files %{_bindir}/* %{_datadir}/%{name} %{_datadir}/applications/* %{_datadir}/pixmaps/* %{_iconsdir}/hicolor/*/apps/* #---------------------------------------------------------------------------- %prep %setup -qn VeraCrypt-VeraCrypt_%{version} %patch1 -p1 %patch2 -p1 %build pushd src %make popd pushd src/Resources/Icons convert VeraCrypt-16x16.xpm VeraCrypt-16x16.png convert VeraCrypt-48x48.xpm VeraCrypt-48x48.png popd rm -f src/Setup/Linux/usr/bin/veracrypt-uninstall.sh %install cp -r src/Setup/Linux/usr %{buildroot} mkdir -p %{buildroot}%{_iconsdir}/hicolor/16x16/apps/ mkdir -p %{buildroot}%{_iconsdir}/hicolor/48x48/apps/ install -m 0644 src/Resources/Icons/VeraCrypt-16x16.png %{buildroot}%{_iconsdir}/hicolor/16x16/apps/%{name}.png install -m 0644 src/Resources/Icons/VeraCrypt-48x48.png %{buildroot}%{_iconsdir}/hicolor/48x48/apps/%{name}.png %changelog * Fri Mar 31 2017 Sébastien B <vigenmailbox@gmail.com> 1.19-1 - For Mageia 6 Regards, Vigen.
CC: (none) => vigenmailbox
Created attachment 9226 [details] .spec
Hi, We currently have 1.19 in the repos. Could it be updated to the latest 1.21 ? https://www.veracrypt.fr/code/VeraCrypt/ Thanks!
CC: (none) => mageia
I'm closing the initial package request as veracrypt has already been added to our repos.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED