[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D33D6213-04DF-4096-8617-F57AD3C73862@gmail.com>
Date: Fri, 5 Aug 2016 17:50:39 +0200
From: "websiteaccess@...il.com" <websiteaccess@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: SSL headers and JTR compile on MAC
> Le 4 août 2016 à 14:45, Albert Veli <albert.veli@...il.com> a écrit :
>
> I can verify that the brew.sh method works.
>
> Remember to use brew link openssl --force. I missed that first. It doesn't
> work without the link command. The brew help text says:
>
> Generally there are no consequences of this for you. If you build your
> own software and it requires this formula, you'll need to add to your
> build variables:
>
> LDFLAGS: -L/usr/local/opt/openssl/lib
> CPPFLAGS: -I/usr/local/opt/openssl/include
>
> These can be added to the john Makefile (around line 53 and line 60)
> instead of forcing the link. An alternative would be to add openssl-libs
> and openssl-cflags options to configure. I have seen some other packages
> with these configure options.
>
> On Thu, Aug 4, 2016 at 12:06 PM, Solar Designer <solar@...nwall.com> wrote:
>
>> On Thu, Aug 04, 2016 at 08:56:33AM +0200, websiteaccess@...il.com wrote:
>>> Thanks for your reply, but how install these openssl development files ?
>>>
>>>> Le 3 ao??t 2016 ?? 19:59, Matus UHLAR - fantomas <uhlar@...tomas.sk>
>> a ??crit :
>>>> you need openssl development files.
>>
>> Guys, please try to keep your postings actually useful. Neither of the
>> two above was useful: a non-helpful answer, and an obvious rewording of
>> the question. Also, W.A., please don't top-post.
>>
>> Apple says:
>>
>> http://lists.apple.com/archives/macnetworkprog/2015/Jun/msg00025.html
>>
>> "We recommend that developers who need OpenSSL build their own copy of
>> it and include that copy in their app. Alternatively you can use native
>> OS X APIs, like Secure Transport."
>>
>> Other OpenSSL-using projects and their users are typically posting this
>> kind of instructions for installing OpenSSL with Homebrew:
>>
>> http://brew.sh
>> https://github.com/phusion/passenger/issues/1630#issuecomment-147464414
>> https://solitum.net/openssl-os-x-el-capitan-and-brew/
>> http://stackoverflow.com/questions/32960032/nginx-cannot-find-openssl-
>> development-headers/32964832#32964832
>>
>> An excessive superset of those appears to be:
>>
>> brew doctor
>> brew update
>> brew upgrade
>> brew install openssl
>> brew link openssl --force
>> cd /usr/local/include
>> ln -s ../opt/openssl/include/openssl .
>>
>> Per a GitHub comment above, this might also work:
>>
>> xcode-select --install
>> cd /usr/local/include
>> ln -s ../opt/openssl/include/openssl .
>>
>> The symlink should take care of the JtR build finding the headers.
>> For linking, you might (or might not) also need
>> "-L/usr/local/opt/openssl/lib" added to LDFLAGS.
>>
>> Some other people are building OpenSSL from source manually:
>>
>> http://mac-dev-env.patrickbougie.com/openssl/
>>
>> If you do this, you should preferably verify the signature on your
>> download before extracting the tarball, and avoid building as root.
>>
>> I haven't tested any of this. W.A., or anyone, if you do, please post
>> in here to let us know which of these worked for you, and please be
>> specific about issues you might run into and work around, if any.
>>
>> Alexander
>>
Hi
I have updated openSSL to 1.0.2
as indicated :
----------------------------------------
brew doctor
brew update
brew upgrade
brew install openssl
brew link openssl --force
cd /usr/local/include
ln -s ../opt/openssl/include/openssl .
Per a GitHub comment above, this might also work:
xcode-select --install
cd /usr/local/include
ln -s ../opt/openssl/include/openssl .
————————————————————
Later, I have downloaded JTR john-1.8.0-jumbo-1
I did :
xxx$ cd /Users/xxx/Desktop/john-1.8.0-jumbo-1/src
then
serviioimac-de-xxxlocal:src xxx$ ./configure && make
Here the output log
checking build system type... x86_64-apple-darwin15.6.0
checking host system type... x86_64-apple-darwin15.6.0
checking whether to compile using MPI... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking additional paths... -L/usr/local/lib -I/usr/local/include
checking arg check macro for -m with gcc... yes
checking arg check macro for -Q with gcc... yes
checking if gcc supports -funroll-loops... yes
checking if gcc supports -Os... yes
checking if gcc supports -finline-functions... no
checking if gcc supports -Wall... yes
checking if gcc supports -Wdeclaration-after-statement... yes
checking if gcc supports -fomit-frame-pointer... yes
checking if gcc supports --param allow-store-data-races=0... no
checking if gcc supports -Wno-deprecated-declarations... yes
checking if gcc supports -Wno-format-extra-args... yes
checking if gcc supports -Qunused-arguments... yes
checking whether ln -s works... yes
checking for grep that handles long lines and -e... /usr/bin/grep
checking for a sed that does not truncate output... /usr/bin/sed
checking for GNU make... make
checking whether make sets $(MAKE)... yes
checking how to run the C preprocessor... gcc -E
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for sort... /usr/bin/sort
checking for ar... /usr/bin/ar
checking for find... /usr/bin/find
checking for pkg-config... no
checking if pkg-config will be used... no
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking size of char... 1
checking size of unsigned char... 1
checking size of short... 2
checking size of unsigned short... 2
checking size of int... 4
checking size of unsigned... 4
checking size of unsigned int... 4
checking size of long... 8
checking size of long long... 8
checking size of double... 8
checking size of long double... 16
checking size of int *... 8
checking size of long long *... 8
checking size of void *... 8
configure: Testing build host's native CPU features
checking for MMX... yes
checking for SSE2... yes
checking for SSSE3... yes
checking for SSE4.1... yes
checking for AVX... yes
checking for AVX2... yes
checking for XOP... no
checking for arch.h alternative... x86-64.h
checking whether compiler understands -march=native... yes
checking for 32/64 bit... 64-bit
checking for extra ASFLAGS... -DUNDERSCORES -DBSD -DALIGN_LOG
checking for X32 ABI... no
checking for unaligned memory access allowed... yes
checking for byte ordering according to target triple... little
checking additional paths for OpenSSL... none
checking openssl/opensslv.h usability... yes
checking openssl/opensslv.h presence... yes
checking for openssl/opensslv.h... yes
checking for SSL_library_init in -lssl... no
configure: error: in `/Users/xxx/Desktop/john-1.8.0-jumbo-1/src':
configure: error: JtR requires libssl being installed
See `config.log' for more details
serviioimac-de-xxxlocal:src xxx$
### ERROR -> configure: error: JtR requires libssl being installed
Pffffffff . Some years ago it was easy to compile JTR for newbie as I am.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
