FS#63981 - [john] kirbi2john is using the wrong interpreter

Attached to Project: Community Packages
Opened by Miles Whittaker (mjwhitta) - Tuesday, 01 October 2019, 17:38 GMT
Last edited by Toolybird (Toolybird) - Saturday, 29 April 2023, 00:54 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

kirbi2john doesn't currently work b/c the interpreter is set to "/usr/bin/env python" instead of "/usr/bin/env python2". This likely applies to many other scripts.

Additional info:
* package version(s)

* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 29 April 2023, 00:54 GMT
Reason for closing:  None
Additional comments about closing:  python2 is long gone.
Comment by Doug Newgard (Scimmia) - Tuesday, 01 October 2019, 17:41 GMT
What's the error?
Comment by Miles Whittaker (mjwhitta) - Tuesday, 01 October 2019, 17:47 GMT
The error is that python points to python3 and NOT python2, but kirbi2john (and it looks like 70+ others) are written in python2.
Comment by Miles Whittaker (mjwhitta) - Tuesday, 01 October 2019, 17:50 GMT
I fixed with a simple sed command: sudo sed -i -r "s/#\!.+python.?$/#\!\/usr\/bin\/env python2/g" /usr/lib/john/*.py
Comment by Doug Newgard (Scimmia) - Tuesday, 01 October 2019, 18:16 GMT
That is not an error message.
Comment by Miles Whittaker (mjwhitta) - Tuesday, 01 October 2019, 18:40 GMT
kirbi2john doesn't throw any errors. It silently fails. This should likely be fixed upstream, but sed could be a workaround until it's fixed. Otherwise, portions of this package are unusable.

Loading...