I have a kinda problem about john
in Kali x86. To make long story short, I can't allow to run john
under Kali Linux 2.0 installed into LV, but as I remember I was able to run in older Kali and older version of john in VM. The error is:
Sorry, SSE2 is required for this build
Well the Kali runs with an enough cpu I think, so I looked it and for each core came out as:
root@kali:~# cat /proc/cpuinfo
model name : Intel(R) Core(TM)2 Duo CPU T5800 @ 2.00GHz
microcode : 0xa4
cpu MHz : 800.000
cache size : 2048 KB
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor
ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm
And, the result of dmidecode
:
root@kali:~# dmidecode -t 4
# dmidecode 2.12
SMBIOS 2.4 present.
Handle 0x001E, DMI type 4, 35 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Pentium M
Manufacturer: Intel(R) Corporation
ID: FD 06 00 00 FF FB EB BF
Signature: Type 0, Family 6, Model 15, Stepping 13
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM)2 Duo CPU T5800 @ 2.00GHz
Voltage: 1.6 V
External Clock: 800 MHz
Max Speed: 2000 MHz
Current Speed: 1200 MHz
Status: Populated, Enabled
Upgrade: <OUT OF SPEC>
L1 Cache Handle: 0x0021
L2 Cache Handle: 0x001F
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: FFFF
Part Number: Not Specified
The result of uname
root@kali:~# uname -a
Linux kali 4.0.0-kali1-686-pae #1 SMP Debian 4.0.4-1+kali2 (2015-06-03) i686 GNU/Linux
The result of gcc version
root@kali:~# gcc --version
gcc (Debian 4.9.2-10) 4.9.2
However I installed John the Ripper 1.8
besides the one came preloaded with Kali Linux distribution and I didn't meet any benchmark for SSE2 during the compiling process.
- So, what is SSE2 in general?
- Can SS2E be used in x86 processors?
- Why do those builds like john need SSE2?
EDIT:
- Why can not those builds be run on a system which has SSE2 specification?
Thanks in advance.
Best Answer
SSE2 is a extended specialized instructions sub-set of Intel x86 instruction set. They are dedicated to SIMD (Single-Instruction Multiple Data) which means that in one instruction they can handle several data thanks to specific extra-wide registers (namely the XMM registers which are 128-bits wides).
The possible splits of the XMM registers are as shown in the following picture.
Any relatively recent Intel x86 processor has SSE2 instruction set. If you want to check if you CPU has it, just do:
You can see here all the instruction sub-sets that your processor has built-in. You should find
sse2
in the list (it is the case here).SEE are really useful for handling signal processing and highly parallelized algorithms. In the case of John the Ripper, SSE2 instruction set is used to parallelized the hash-function brute-force algorithm. It computes several hash attempts in one instruction to speed-up the exploration of the key-space (or to exhaust the dictionnary).
It is very likely linked to a software reason. Either you installed 32bits system over a 64bits CPU (i386 over amd64), or you may not have the compile tools that are able to handle SSE2 instruction sets. It also may be because the build-system of John has a flaw and failed to detect properly the ability of your system.
But, you do not give enough information about your system to solve the problem.
If you want to install
john
, you better use the pre-compiled package that comes with your distribution (this is a standard package in almost any mainstream distribution now).