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
FreeBSD support #34
Comments
Hi, Few months ago, I looked at the possibility of a FreeBSD port because there is already some code for it that is inherited from TrueCrypt. I didn't spend a lot of time so maybe I missed something obvious. Any help from BSD developers would be much appreciated. |
Do you mean mount_fusefs(8)? That's what libfuse uses under the hood. On FreeBSD 9.x (and 8.x a few months back) mount_fusefs is provided via sysutils/fusefs-kmod port. I was curious and built VeraCrypt but it worked fine as is. Looking closer at Process::Execute implementation it seems |
Hi idrassi, It is good to hear that you already tried making it work. I forwarded info about this thread to the FreeBSD "ports" mailing list, as I'm not skilled enough to help you. Hopefully somebody knowledgeable chips in. :-) This is the Link to the thread: https://lists.freebsd.org/pipermail/freebsd-ports/2015-December/101254.html |
I could compile it easily (but still have some problems with WXWidgets so no UI). For fuse there used to be "sysutils/fusefs-kmod" in Ports but its now built-in by default. So all you need to do is adding |
@engerim42 It sounds great that you got it working. There is a official guide how to build VeraCrypt for Linux and Mac. |
Any chance for progress on this? |
@agilob didn't have much time recently. if you follow my instructions above it should work well though (but without UI) |
+1 to make VeraCrypt work on FreeBSD! :-) |
There's only two line changes needed to the Makefile for VeraCrypt to build and, apparently, run just fine on FreeBSD 10.3 including UI support. I've always wanted to create a port... |
@microshaft please let us know if you're planning to make it and if so, when it's ready! |
@idrassi are you planning to release 1.20 soon? 1.19 doesn't build on FreeBSD but the current master does. |
Yes, I'm planning to release 1.20 very soon. It was expected to come few weeks ago but I had some private issues that didn't allow me to work on it. Moreover, I have a modification for FreeBSD 11 that I didn't commit yet related to compiler and filemanager detection. Below is a copy of the patch. I will push it as soon as possible. Don't hesitate to share any modification that maybe needed.
|
I've been working on a port to FreeBSD 11 also.
I had hoped to get it out a couple of weeks ago, but other events
intervened. I hope to have some time to work on it this weekend.
I'll incorporate this into my build and let you know how it works.
…On 02/16/2017 09:06 AM, Mounir IDRASSI wrote:
Yes, I'm planning to release 1.20 very soon. It was expected to come
few weeks ago but I had some private issues that didn't allow me to
work on it.
Moreover, I have a modification for FreeBSD 11 that I didn't commit
yet related to compiler and filemanager detection. Below is a copy of
the patch. I will push it as soon as possible.
Don't hesitate to share any modification that maybe needed.
|--- src/Main/UserInterface.cpp | 6 +++--- src/Makefile | 18
++++++++++++++++++ 2 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/src/Main/UserInterface.cpp b/src/Main/UserInterface.cpp
index fa2088f..c79cef2 100644 --- a/src/Main/UserInterface.cpp +++
b/src/Main/UserInterface.cpp @@ -838,12 +838,12 @@ namespace VeraCrypt
#else // MIME handler for directory seems to be unavailable through
wxWidgets wxString desktop = GetTraits()->GetDesktopEnvironment(); -
bool xdgOpenPresent = wxFileName::IsFileExecutable
(wxT("/usr/bin/xdg-open")); - bool nautilusPresent =
wxFileName::IsFileExecutable (wxT("/usr/bin/nautilus")); + bool
xdgOpenPresent = wxFileName::IsFileExecutable
(wxT("/usr/bin/xdg-open")) || wxFileName::IsFileExecutable
(wxT("/usr/local/bin/xdg-open")); + bool nautilusPresent =
wxFileName::IsFileExecutable (wxT("/usr/bin/nautilus")) ||
wxFileName::IsFileExecutable (wxT("/usr/local/bin/nautilus")); if
(desktop == L"GNOME" || (desktop.empty() && !xdgOpenPresent &&
nautilusPresent)) { - args.push_back ("--no-default-window"); + //
args.push_back ("--no-default-window"); // This option causes nautilus
not to launch under FreeBSD 11 args.push_back ("--no-desktop");
args.push_back (string (path)); try diff --git a/src/Makefile
b/src/Makefile index dea172f..1b71f27 100644 --- a/src/Makefile +++
b/src/Makefile @@ -285,6 +285,24 @@ ifeq "$(shell uname -s)" "FreeBSD"
PLATFORM := FreeBSD PLATFORM_UNSUPPORTED := 1 C_CXX_FLAGS += -DTC_UNIX
-DTC_BSD -DTC_FREEBSD + + CC := cc + CXX := c++ + + ifeq
"$(SIMD_SUPPORTED)" "1" + CFLAGS += -msse2 -maes + CXXFLAGS += -msse2
-maes + + ifeq "$(origin SSSE3)" "command line" + CFLAGS += -mssse3 +
CXXFLAGS += -mssse3 + endif + + ifeq "$(origin SSE41)" "command line"
+ CFLAGS += -mssse3 -msse4.1 + CXXFLAGS += -mssse3 -msse4.1 + endif +
endif endif -- |
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABpRjsk18CnmRB-bOo7C7V1KZ8BOlCqQks5rdFf8gaJpZM4GnyBg>.
|
I just submitted the FreeBSD port for this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217775 I'm not a committer, but you should be able to use the SVN diff I submitted with this bug to insert it into your ports tree under security/veracrypt. I have not extensively tested this port, but I have been able to build it and run it successfully on an AMD powered FreeBSD 11 desktop as well as an Atom powered netbook running GhostBSD (FreeBSD 10.3-RELEASE). I should also add that I did not incorporate the above code from @idrassi. The port is based on commit 100b79d from Jan 23. |
Awsome will try to verify in a free moment :-) |
Having this on FreeBSD would be great since FreeNAS uses this as their OS of choice (and the latest, FreeNAS 11 is using FreeBSD11). I hope it will be possible to release this because my current workaround is amazingly bad - run a VM on the FreeNAS system, in this VM, run something like centos or ubuntu, use NFS/SMB to mount the volume and then work on the files :D but it's obviously super tedious and slow, not to mention the extra strain on system resources unlike a native program. @idrassi welcome back, too! |
Finally there is a FreeBSD Port now: Thanks to all people involved! |
AWSOME! CONGRATZ!! :-)
…--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
|
Hello,
and thanks for developing VeraCrypt.
FreeBSD gains more and more end users. Not only because of but with a lot of help from PC-BSD. It would be great to have VeraCrypt port in the ports collection of FreeBSD.
For me personally it would be great to have access to some of my in Windows encrypted HDDs. This would improve and extend this great multi platform encryption system.
Any thoughts on the Issue?
The text was updated successfully, but these errors were encountered: