WX_CONFIGURE_FLAGS += -enable-debug_gdb -enable-debug_info WX_CONFIGURE_FLAGS += -enable-debug_flag -disable-debug_gdb -disable-debug_info WX_CONFIGURE_FLAGS += -disable-debug_flag -disable-debug_gdb -disable-debug_infoĬXXFLAGS += -fno-default-inline -Wno-unused-function -Wno-unused-variableĮxport WX_BUILD_DIR ?= $(BASE_DIR)/wxdebug Ifeq "$(origin RESOURCEDIR)" "command line"Ĭ_CXX_FLAGS += -DTC_RESOURCE_DIR="$(RESOURCEDIR)"Ĭ_CXX_FLAGS += -O2 -fno-strict-aliasing # Do not enable strict aliasingĮxport WX_BUILD_DIR ?= $(BASE_DIR)/wxrelease # wxbuild: Configure and build wxWidgets - source code must be located at $(WX_ROOT)Įxport BUILD_INC := $(BASE_DIR)/Build/IncludeĮxport CXXFLAGS := -Wall -Wno-unused-parameterĬ_CXX_FLAGS := -MMD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES -I$(BASE_DIR) -I$(BASE_DIR)/CryptoĮxport PKG_CONFIG_PATH ?= /usr/local/lib/pkgconfig I tried taking information from other blogs and applying it to my situation but i don't fully understand linking libs yet so i cant figure this thing out without more specifics. How would i modify that exactly? I've read that link you sent before and i know it's related to my problem but could not figure out what exactly to type into my command line or what to do really. Thankyou but how exactly would i do that? Truecrypt doesn't have configure files just a make file as far as i can see. Makefile:268: recipe for target 'all' failed Main.make:107: recipe for target 'truecrypt' failed usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO missing from command lineĬollect2: error: ld returned 1 exit status usr/bin/ld: /usr/src/truecrypt-7.1a-source/wxrelease/lib/libwx_gtk2u_core-2.8.a(corelib_utilsx11.o): undefined reference to symbol 'XGetWindowAttributes' I have also tried to type -lx11 into the command line after that error and it says bash: -lx11: command not found Please help me i know you guys are smart. Even if i compile and install wxwidgets-2.8.12 myself i get this error. That completes than i run make WXSTATIC=1 and i run into this error below. I'm not sure how to fix that so i went to option 2 compile wxgtk2.8.12 source using the truecrypt compile option make WX_ROOT=/usr/src/truecrypt-7.1a-source/wxGTK-2.8.12 wxbuild. I have wxGTK2.8.12 source because geniuses at deb Jessie only have v3.0 packages thats a problem because wxwidgets3.0 has protected wxstandardpaths so you have to use wxstandardpaths::get and truecrypt uses wxstandardpaths in application.cpp for example and would return an error while compiling. Coming in early 2015, Gears will add support for generic encryption detection when the software used is unknown!įor more information, please contact one of our cybersecurity experts.What's up guys so I've been trying too compile truecrypt 7.1a on Debian Jessie 8.1.0 AMD64 for the past two days now.yes you heard that right lol I've done everything i could think of researching nonstop along the way and frankly I'm starting to get pissed at blogs saying hit make and enjoy here is where I'm at now. This encryption detection ability in Gears is included in even the free accounts (up to 25 devices) and supports the most popular encryption products. The admin can even gain awareness if the user pauses or suspends encryption, or has additional partitions without encryption. Within a few minutes, the dashboard will show which devices are and aren't encrypted. An admin can install Gears on owned device, and/or ask BYOD owners to run Gears on-demand. I'd wager that anything the NSA struggles to crack is certainly good enough for most consumers and businesses!įor businesses that need to enforce disk encryption, using TrueCrypt or other technology, Gears provides simple and robust detection and reporting. Some of the other 'most wanted' list members have been cracked by the NSA in the last couple years, including Tor, but it is unclear what progress the they have made on cracking TrueCrypt, if any, since 2012. Additionally, recent revelations from Edward Snowden have shown that the National Security Administration had TrueCrypt on their 'most wanted' list for decryption as recently as 2012. ZDNet recently put out a great article, '10 Best Privacy Tools for Staying Secure Online', where TrueCrypt technology still comes in the #3 spot. €‹TrueCrypt's staying power has been proven again and again. Considering its popularity and the general response by the public, it was no surprise that within a few months a group of developers have revived this open source stalwart by forking the code into CipherShed. In mid-2014, to the chagrin of many, TrueCrypt development was discontinued.
0 Comments
Leave a Reply. |