Skip to content

Instantly share code, notes, and snippets.

@reggi
Last active March 30, 2022 08:39
Show Gist options
  • Save reggi/2faadedd925789a3d25196f2a036ecc6 to your computer and use it in GitHub Desktop.
Save reggi/2faadedd925789a3d25196f2a036ecc6 to your computer and use it in GitHub Desktop.
Building John The Ripper on OSX.
@rgov
Copy link

rgov commented Mar 9, 2018

You should use $(brew --prefix) when possible instead of hard-coding Homebrew paths.

./configure CPPFLAGS="-I$(brew --prefix openssl)/include" LDFLAGS="-L$(brew --prefix openssl)/lib" --disable-pkg-config

@R3dy
Copy link

R3dy commented Mar 20, 2019

Some great comments here, thanks a bunch to @mubix and @rgov

My mileage varied slightly but in the end this is what worked for me on a 2018 Macbook Pro running Mojave. This was after installing gcc and openssl via brew. Notice the CFLAGS instead of CPPFLAGS

./configure CC="gcc-8" CFLAGS="-I$(brew --prefix openssl)/include" LDFLAGS="-L$(brew --prefix openssl)/lib" --disable-pkg-config

@alexeynikolayev
Copy link

Getting stuck on catalina :(

checking additional paths for OpenSSL... none
checking openssl/opensslv.h usability... no
checking openssl/opensslv.h presence... yes
configure: WARNING: openssl/opensslv.h: present but cannot be compiled
configure: WARNING: openssl/opensslv.h:     check for missing prerequisite headers?
configure: WARNING: openssl/opensslv.h: see the Autoconf documentation
configure: WARNING: openssl/opensslv.h:     section "Present But Cannot Be Compiled"
configure: WARNING: openssl/opensslv.h: proceeding with the compiler's result
configure: WARNING:     ## ------------------------------------------------------ ##
configure: WARNING:     ## Report this to john-users mailing list at openwall.com ##
configure: WARNING:     ## ------------------------------------------------------ ##
checking for openssl/opensslv.h... no
configure: error: in `/Users/user/temp/jumbo/src':
configure: error: JtR requires OpenSSL headers being installed
See `config.log' for more details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment