-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Port to Python 3 #317
Comments
I am aware, efforts on this have been ongoing for a while I've been getting side tracked with some other projects of mine. Next month (October 2019) will be the official "Port CME to Python3" Month. |
I was ready to do it, but noticed that pywerview is not ported to python3 so I don't see how it is possible to port CME to python3 :'( |
Turns out I started to migrate the project to python3 https://github.com/mpgn/CrackMapExec/tree/python3 Of course, I migrate the pywerview to python3 too. Here is a preview for tonight ! |
I'm starting the fire #323 :) |
Damn, this is crazy. Thanks for the help! |
Tried an install on 3.8 - Failed on https://github.com/dlitz/pycrypto - Which hasn't received a commit in the past 6 years and likely never will :p |
Very strange since CME doesn't use pycrypto anymore 333f1c4 ... |
Hello, what's the current status for the Python 3 port ? It's getting harder for us (Kali) to keep crackmapexec with Python 2, Debian has already dropped the Python 2 version of impacket. https://www.dlitz.net/software/pycrypto/ is available for Python 3 in Debian/Kali at least, even if it hasn't changed since a long time, its setup.py indicates Python 3 support. There are a couple of patches in the Debian package though: https://sources.debian.org/src/python-crypto/2.6.1-13/debian/patches/ Anyway I don't think that pycrypto should be a blocker. |
Hi @rhertzog CME is already ported to python3, we are waiting for the approval of @byt3bl33d3r to merge into the branch python3 of CME. The project has also the dependency pywerview (python2 project) the-useless-one/pywerview#34 where I'm also waiting for the PR (we don't even need to be on the master branch) - but this part is not a blocker since we can use my fork of their repo. More info: #323 As for the pycrypto problem, I've tested CME python3 in Kali and I didn't encountered the problem described by Reelix. |
@mpgn Do you consider both of your PR as ready? If yes, we can already package your forks in Kali until we have proper upstream releases. |
Hello @rhertzog I've contact directly @byt3bl33d3r and he tells me that he has to deal with other issues first. He didn't forget us, he just has more important priorites :)
Not an ideal solution because I'm afraid people will still open issue on this github while the issue maybe related to the python3 CME project. I've tested to run my PR on latest Kali using this lines and CME is working fine on my side. git clone --recursive https://github.com/mpgn/CrackMapExec && cd CrackMapExec
git submodule update --recursive
python3 setup.py install
cme |
Hi @mpgn , thanks a lot for taking the initiative. I'm having a minor issue with python3, clould you have a look at the following please:
|
There is also one more issue with slinky.py module. It requires |
@mpgn thanks. Can you also fix a bunch of prints which I posted above? Update: all errors are related to the invoke-vnc external module. |
PR submitted to the Invoke-vnc project @blshkv :) |
@mpgn I have merged all patches, managed to install, start and tested some basic functionality. |
Closing this one since the python3 PR is merged 🖌️ |
sorry, I can't find this commit and the merge pull request is still opened |
can you elaborate ? |
I have pulled the latest git version https://github.com/byt3bl33d3r/CrackMapExec.git master, e294a72 commit and still see the same errors as reported. I can still apply the same patch from the pull request |
I see, I forgot about this one @blshkv but I already take care of the problem. Nevertheless, I cannot do much if no one wants to merge my PR . . . |
We can use my fork in the meantime :) |
Please keep this bug open until someone will find a power to press that damn merge button :-) |
@blshkv Just for my clarity, are you getting errors when packaging CME cause of the VNC script thing? |
@byt3bl33d3r hm... I just realized that you have merged #323 pull request yesterday. My apologies, this bug can be closed! These are remaining external modules: |
This should do the work :) |
Hello,
Python 2.x will no longer be supported by their upstream developers in 2020. Thus Debian developers are actively removing Python 2 support in Debian Testing with the goal of getting rid of Python 2 in Debian 11 (bullseye).
Kali is tracking Debian Testing and is thus affected by this. You should consider to switch crackmapexec to Python 3.
FWIW this is tracked in https://gitlab.com/kalilinux/packages/crackmapexec/issues/1 on the Kali side.
The text was updated successfully, but these errors were encountered: