View Issue Details

IDProjectCategoryView StatusLast Update
0002994Kali LinuxKali Package Bugpublic2016-01-18 10:53
Reporterdookie Assigned Torhertzog  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version2016.1 
Fixed in Version2016.1 
Summary0002994: John the Ripper Fails to Run
Description

John the Ripper (john) and its utilities (i.e. unshadow) fail to run and display the following message:

root@kali:~# john
Sorry, XOP is required for this build

root@kali:~# unshadow
Sorry, XOP is required for this build

Additional Information

This is running on kali-rolling amd64:

root@kali:~# uname -a
Linux kali 4.3.0-kali1-amd64 0000001 SMP Debian 4.3.3-5kali2 (2016-01-08) x86_64 GNU/Linux

It seems that this is a somewhat-known issue in that it has at least appeared before:

http://comments.gmane.org/gmane.comp.security.openwall.john.user/8425

Activities

rhertzog

rhertzog

2016-01-18 09:31

administrator   ~0004510

Do you have this with kali-rolling and john 1.8.0.6-jumbo-1-0kali6 ?

rhertzog

rhertzog

2016-01-18 09:34

administrator   ~0004511

Because this bug is sort of expected with 1.8.0.6-jumbo-1-0kali2 in sana but it has been fixed with 1.8.0.6-jumbo-1-0kali3.

rhertzog

rhertzog

2016-01-18 09:37

administrator   ~0004512

Bah, I can reproduce it on Kali Rolling. I'm sure I had tested this when I added the fallback machinery. I will investigate...

rhertzog

rhertzog

2016-01-18 10:53

administrator   ~0004513

Fixed in john_1.8.0.6-jumbo-1-0kali7.dsc that I just uploaded to kali-dev.

It turns out I fixed it in kali3 but broke it again in kali6 with some simple cleanups made in debian/rules....

Issue History

Date Modified Username Field Change
2016-01-15 22:09 dookie New Issue
2016-01-15 22:09 dookie Status new => assigned
2016-01-15 22:09 dookie Assigned To => rhertzog
2016-01-18 09:31 rhertzog Note Added: 0004510
2016-01-18 09:34 rhertzog Note Added: 0004511
2016-01-18 09:37 rhertzog Note Added: 0004512
2016-01-18 10:53 rhertzog Note Added: 0004513
2016-01-18 10:53 rhertzog Status assigned => resolved
2016-01-18 10:53 rhertzog Fixed in Version => 2016.1
2016-01-18 10:53 rhertzog Resolution open => fixed