The current upstream release is 1.9.0. Please bump.
And it seems we probably need the -jumbo branch which support other file formats via plugins. Looks there is even pkcs12 plugin for john.
An einfo() message pointing to https://openwall.info/wiki/john/johnny would be helpful too.
While at it, https://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/john/john/doc/CHANGES speaks of:
Revision 1.111: download - view: text, markup, annotated - select for diffs
Sat Mar 23 12:15:28 2019 UTC (9 months, 1 week ago) by solar
Diff to: previous 1.110: preferred, colored
Changes since revision 1.110: +3 -3 lines
- Added runtime detection of AVX2 and AVX-512, loosely based on work by magnum
in jumbo (thanks!)
- Added linux-x86-avx512 and linux-x86-avx2 make targets (32-bit, mostly for
testing in case the 32-bit AVX2 code is later needed e.g. for a Win32 build).
Revision 1.110: download - view: text, markup, annotated - select for diffs
Fri Mar 22 11:28:58 2019 UTC (9 months, 1 week ago) by solar
Diff to: previous 1.109: preferred, colored
Changes since revision 1.109: +5 -3 lines
- Added linux-x86-64-avx512 and linux-x86-64-avx2 make targets, which use
respectively AVX-512 and AVX2 for bitslice DES.
- Dropped use of 256-bit AVX (the original "floating point" one) in 32-bit
builds, dropped compile-time support for other weird bitslice DES vector types
(these were for experiments only and didn't provide performance improvement on
almost any real hardware).
I think the USE flags will need adjustments. At the moment I have:
[ebuild R ] app-crypt/johntheripper-1.8.0::gentoo USE="openmp -custom-cflags" CPU_FLAGS_X86="avx sse2 (-mmx) -xop" 0 KiB
The following explains that only the highest CPU_FLAGS_X86 value should be passed to configure: https://www.openwall.com/lists/john-users/2019/06/24/3