Hello Sandro Upstream seems a bit stalled but there is a patch (by Kimocoder from aircrack project) to migrate it. You can see it here:
https://github.com/JPaulMora/Pyrit/pull/593 As i have some time these days,i will try to test it a see if it is a valid approach. Greetings, Marcos El mié, 18-03-2020 a las 19:43 -0400, Sandro Tosi escribió: > Hello everyone, > > On Fri, 30 Aug 2019 07:35:12 +0000 Matthias Klose <d...@debian.org> > wrote: > > Package: src:pyrit > > Version: 0.5.1+git20180801-1 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > What is the future for pyrit? i see upstream published 3 months ago > that: > > ``` > Pyrit is old, is outdated and it's still Python2 I am currently > attempting to rewrite it from scratch, so thanks for all the stars > but > remember to keep an eye for Python3 version. > ``` > > and Raphael pinged upstream regarding where to actual "watch" for > this > new version: > https://github.com/JPaulMora/Pyrit/issues/200#issuecomment-581859819 > > but nothing really happened in between: i could see no public > progress > from upstream, and only visible push towards python3 compatibility is > this PR which is now https://github.com/JPaulMora/Pyrit/pull/593 3 > months old with no comments or sign of an imminent merge. > > the reason i'm here is because pyrit is the last reverse dependency > of > python-scapy, which in turn is the last reverse dependency of > ipython. > > since i dont know when (and even if) a pyrit python3 port will be > available, i was considering removing it (which will also require > removing the b-d from wifite) so that scapy and ipython can drop > their > python2 support. > > What do you guys think about this approach? I would like to proceed > quickly so please reply withing a week or two. > > Regards, > Sandro
