ToDo: Transit Pyrit to Python 3

[GoogleCodeExporter]

After recent update to Python 3 it seem to break the pyrit usability. Not sure 
if this is something related to Archlinux itself or that it might be something 
that needs to be changed in Pyrit. However i quote: 

"AUR and third-party packages/projects using Python will likely need updating 
to reflect this move, as many programs are still incompatible with Python 3."

Meaning it might affect Pyrit itself.

What steps will reproduce the problem?
1. Updating to Python 3 in Archlinux
2. Try to run 'pyrit batch'

What is the expected output? What do you see instead?
The expected output is that pyrit start batching the wordlists. 

But instead it gives me the output found in attached logfiles for both 
reinstalling pyrit and trying to run pyrit batch.

What version of the product are you using? On what operating system?
Pyrit 0.3.0-3 @ Archlinux

Additional information might found here:
https://bbs.archlinux.org/viewtopic.php?id=106958
http://www.archlinux.org/news/python-is-now-python-3/
http://allanmcrae.com/2010/10/big-python-transition-in-arch-linux/

Original issue reported on code.google.com by niclas.k...@gmail.com on 20 Oct 2010 at 10:49

Attachments:

• reinstall_pyrit
• run_pyrit_batch

[GoogleCodeExporter]

Pyrit is written for Python 2.x which is not compatible out of the box with 
Python3. This is especially true for C-extension which Pyrit makes heavy use 
of. As http://www.archlinux.org/news/python-is-now-python-3/ says, the package 
in arch needs to patch /usr/bin/pyrit (which loads the rest of Pyrit) to 
execute with /usr/bin/python2 instead of /usr/bin/python

Original comment by lukas.l...@gmail.com on 21 Oct 2010 at 6:48

• Changed title: Transit Pyrit to Python 3
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Understood. Now im trying to figure out a patch. But i dont know how to do it, 
if i may once again refer to the forum post on the issue: 
https://bbs.archlinux.org/viewtopic.php?pid=843717#p843717
I've been trying some solutions with no good results. Will pyrit be rewritten 
in any near future to work out of the box with Python 3?

Original comment by niclas.k...@gmail.com on 22 Oct 2010 at 10:43

[GoogleCodeExporter]

that is entirely up to ArchLinux. I don't know how they build their packages, 
but Pyrit must be linked to the 2.x version of the cpython library and 
installed to that site-packages directory. Also see comment #1. You probably 
just have to modify the script/description file/whatever that builds the 
package. See how other packages that *must* be used with 2.x manage to do 
that...

The transition is not going to happen any time soon. Python 2.7 will be around 
for a long time and 3.x is not even available on all platforms yet.

Original comment by lukas.l...@gmail.com on 22 Oct 2010 at 11:12

[GoogleCodeExporter]

r287 can be reverted with Python3

Original comment by lukas.l...@gmail.com on 28 Oct 2010 at 6:18

• Changed title: ToDo: Transit Pyrit to Python 3

[rhertzog]

Hi,

@JPaulMora can you let us know what's the status wrt to switching to Python 3 ?

With the python 2 EOL in 2 months, many projects including Debian and Kali are trying to get rid of Python 2 and pyrit is one of the packages that still needs to be ported.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937521 for the corresponding bug. Note that if it get dropped from Debian, it will also go away from Kali since Kali is getting this package from Debian.

-- Raphaël, Debian/Kali packager.

[rhertzog]

@JPaulMora I saw the README update inviting users to watch for the Python 3 version. But you are not saying where we need to watch. Will this be pushed in this repository? Do you have any idea when the Python 3 port will be ready?