openwall / openwall/john

Unable to build JtR Jumbo on Fire HD 10 tablet

Open
#3,284 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

portability
Dominant language
C
Stars
13.6k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Description

The Fire HD 10 tablet is running Termux (a Linux environment). I am building JtR Jumbo (bleeding-jumbo HEAD) within the Termux environment.

$ gcc --version
clang version 6.0.0 (tags/RELEASE_600/final)
Target: armv7--linux-android
Thread model: posix
InstalledDir: /data/data/com.termux/files/usr/bin
$ ./configure
Configured for building John the Ripper jumbo:

Target CPU ................................. armv8l NEON, 32-bit LE                                          
AES-NI support ............................. no                                                              
Target OS .................................. linux-gnueabi
Cross compiling ............................ no
Legacy arch header ......................... arm32le.h                                                                                                                                                                    

Optional libraries/features found:                                                                           
Memory map (share/page large files) ........ yes
Fork support ............................... yes
OpenMP support ............................. yes (not for fast formats)
OpenCL support ............................. no
Generic crypt(3) format .................... yes
libgmp (PRINCE mode and faster SRP formats)  no
128-bit integer (faster PRINCE mode) ....... no                                                         
libz (pkzip format, gpg2john) .............. yes                                                      
libbz2 (gpg2john extra decompression logic)  no                                                              
libpcap (vncpcap2john and SIPdump) ......... no                                                           
librexgen (regex cracking mode) ............ no                                                            
OpenMPI support (default disabled) ......... no                                                              
ZTEX USB-FPGA module 1.15y support ......... no                                                                                                                                                                           Install missing libraries to get any needed features that were omitted.

Configure finished.  Now "make -s clean && make -sj4" to compile.
$ make
...
gcc -DAC_BUILT -mfpu=neon -DJOHN_NEON -c -g -O2 -DARCH_LITTLE_ENDIAN=1  -Wall -Wdeclaration-after-statement -fno-omit-frame-pointer -Wno-deprecated-declarations -Wformat-extra-args -Qunused-arguments -std=gnu89 -Wdate-time -D_POSIX_SOURCE -D_GNU_SOURCE -D_XOPEN_SOURCE=600 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE   -fopenmp      -funroll-loops rawSHA256_ng_fmt_plug.c -o rawSHA256_ng_fmt_plug.o
In file included from rawSHA256_ng_fmt_plug.c:36:
In file included from ./misc.h:21:
./jumbo.h:145:6: warning: Using 32-bit ftell(). Files larger than 2GB will be handled unreliably
      [-W#warnings]
    #warning Using 32-bit ftell(). Files larger than 2GB will be handled unreliably
     ^                                                                                                       rawSHA256_ng_fmt_plug.c:280:9: error: argument should be a value from 1 to 32                                        SHA256_STEP(a, b, c, d, e, f, g, h,  0, 0x428a2f98);                                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rawSHA256_ng_fmt_plug.c:166:21: note: expanded from macro 'SHA256_STEP'
        if (x > 15) R(x);                           \
                    ^~~~
rawSHA256_ng_fmt_plug.c:159:27: note: expanded from macro 'R'
        w[t] = vadd_epi32(s1(w[t -  2]), w[t - 7]); \
               ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
rawSHA256_ng_fmt_plug.c:143:17: note: expanded from macro 's1'
                vroti_epi32(x, -17),            \
                ^
note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
./pseudo_intrinsics.h:85:51: note: expanded from macro 'vxor'
#define vxor(x, y)              (vtype)veorq_u32((x).v32, (y).v32)
                                                  ^
./pseudo_intrinsics.h:85:60: note: expanded from macro 'vxor'                                                #define vxor(x, y)              (vtype)veorq_u32((x).v32, (y).v32)                                                                                                      ^                                                 ./pseudo_intrinsics.h:54:51: note: expanded from macro 'vadd_epi32'
#define vadd_epi32(x, y)        (vtype)vaddq_u32((x).v32, (y).v32)
                                                  ^                                                          rawSHA256_ng_fmt_plug.c:280:9: error: argument should be a value from 0 to 31                                        SHA256_STEP(a, b, c, d, e, f, g, h,  0, 0x428a2f98);                                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rawSHA256_ng_fmt_plug.c:166:21: note: expanded from macro 'SHA256_STEP'
        if (x > 15) R(x);

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported ./configure and make failure in the Termux environment on the Fire HD 10. Start with rawSHA256_ng_fmt_plug.c and the macro definitions in pseudo_intrinsics.h, then compare the compiler diagnostics around SHA256_STEP and the ARM NEON intrinsics. Done means JtR Jumbo builds successfully on the reported platform.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.