Support for Python 3 #594
Comments
|
I'm not sure if we have people that care about Python3 support - I don't. |
|
I don't either, but as a long term project, Python2 will eventually depricate. |
|
Personally doubt it :p |
|
Currently very unlikely that we'll port to Python 3 any time soon. Closing until this becomes a realistic opportunity. |
|
Is this realistic enough? |
|
Now, seriously, are there any plans regarding python 3 compatibility? |
|
This is on our longterm roadmap - we've already started to port some of our libraries that are used by Cuckoo to be Python 3-compatible (e.g., https://github.com/jbremer/sflock, https://github.com/jbremer/roach) and most of our external dependencies are Python 3-compatible already. Unfortunately Cuckoo becoming both Python 2 and Python 3 compatible (my personal preference for now) is a long development plan requiring lots of manual testing and new unit tests for all the code paths that are currently not tested. Otherwise we'll get daily reports of Concluding: yes, but will take some time still.. unless somebody would like to donate resources in terms of time or money to sponsor such development. |
|
Great! Thanks for the response! |
|
Sure, I guess ;-) |
|
Hi, |
|
Hi @jbremer , |
|
Oh, here is the answer :) :
=> Current version is Python2/3 compatible : No need to update, or few fixes :) [EDIT] |
|
Where does this issue stand? @LetMeR00t has open PRs on the unsupported libraries. It has been 2 months. We're less than 6 months from Python 2 EOL across the board. Cuckoo Sandbox is the only open-source, commercially competitive tool for sandboxing; this project needs to stay alive. The only non-compatible libraries are the ones written by a single GitHub organization (github.com/hatching). Additionally, there isn't a reason to keep support for Python 2, especially because mitmproxy won't work with it on the latest version. Why make it compatible with Python 2, when in 6 months people can't use this software for any project that they're not okay getting wrecked with a Python 2 zero-day. IMO (and I'm sure of many others as well if they realized the full problem), Python 3 should be the only priority until its implemented. Non-critical bugs and stability issues (like rewriting the results processor in the 2.0.7 release) make zero sense when Cuckoo will be unusable for any company or person that only uses officially supported software (here, Python is the underlying foundation that won't be supported for version 2). I see Cuckoo up there with projects like Tensorflow, Requests, and similar major players, and they all moved to Python 3 long ago: https://python3statement.org/. |
|
Hi Jared,
I dont think you will find much argument here. I too am concerned that this
is going to go to the wayside. There are a number of concerning
vulnerabilities in Cuckoo as it currently stands "Python, and ES" being
two.
There is nothing stopping people from forking it, but it would require a
large investment in time to get the architecture under their belt.
Im pretty saddened that its got to this point, ive been a cuckoobox user
since about 2010 and while i do understand that if you are going to do this
full time you need an income, its also important to understand that many
many people have contributed to the project as well.
…On Thu, Jul 4, 2019 at 9:05 AM Jared M. Smith ***@***.***> wrote:
Where does this issue stand? @LetMeR00t <https://github.com/LetMeR00t>
has open PRs on the unsupported libraries. It has been 2 months. We're less
than 6 months from Python 2 EOL across the board.
Cuckoo Sandbox is the *only* open-source, commercially competitive tool
for sandboxing; this project needs to stay alive. The only non-compatible
libraries are the ones written by a single GitHub organization (
github.com/hatching). Additionally, there isn't a reason to keep support
for Python 2, especially because mitmproxy won't work with it on the latest
version. Why make it compatible with Python 2, when in 6 months people
can't use this software for any project that they're not okay getting
wrecked with a Python 2 zero-day.
IMO (and I'm sure of many others as well if they realized the full
problem), Python 3 should be the *only* priority until its implemented.
Non-critical bugs and stability issues (like rewriting the results
processor in the 2.0.7 release) make zero sense when Cuckoo will be
unusable for any company or person that only uses officially supported
software (here, Python is the underlying foundation that won't be supported
for version 2).
I see Cuckoo up there with projects like Tensorflow, Requests, and similar
major players, and they all moved to Python 3 long ago:
https://python3statement.org/.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#594?email_source=notifications&email_token=AEH6FGG3GJF5J52ICABZ3TTP5UIDNA5CNFSM4BJ6ZT62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFVUPA#issuecomment-508254780>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEH6FGBXHNLEYOELL4UHVGTP5UIDNANCNFSM4BJ6ZT6Q>
.
|
|
It's being worked on and it's something the cuckoo developers are well
aware of. Making posts like this does little to add to the conversation or
help in any way.
It's actually ultra toxic and doesn't really inspire motivation to spend
free time helping people that can't help themselves.
Even if cuckoo fully supported 3 volatility and many other projects still
don't. I have cuckoo mostly working in python 3 with only a few bugs to
finish out. Though it will only be useful when major libraries it uses also
move to python 3.
…On Thu, Jul 4, 2019, 3:30 PM SparkyNZL ***@***.***> wrote:
Hi Jared,
I dont think you will find much argument here. I too am concerned that this
is going to go to the wayside. There are a number of concerning
vulnerabilities in Cuckoo as it currently stands "Python, and ES" being
two.
There is nothing stopping people from forking it, but it would require a
large investment in time to get the architecture under their belt.
Im pretty saddened that its got to this point, ive been a cuckoobox user
since about 2010 and while i do understand that if you are going to do this
full time you need an income, its also important to understand that many
many people have contributed to the project as well.
On Thu, Jul 4, 2019 at 9:05 AM Jared M. Smith ***@***.***>
wrote:
> Where does this issue stand? @LetMeR00t <https://github.com/LetMeR00t>
> has open PRs on the unsupported libraries. It has been 2 months. We're
less
> than 6 months from Python 2 EOL across the board.
>
> Cuckoo Sandbox is the *only* open-source, commercially competitive tool
> for sandboxing; this project needs to stay alive. The only non-compatible
> libraries are the ones written by a single GitHub organization (
> github.com/hatching). Additionally, there isn't a reason to keep support
> for Python 2, especially because mitmproxy won't work with it on the
latest
> version. Why make it compatible with Python 2, when in 6 months people
> can't use this software for any project that they're not okay getting
> wrecked with a Python 2 zero-day.
>
> IMO (and I'm sure of many others as well if they realized the full
> problem), Python 3 should be the *only* priority until its implemented.
> Non-critical bugs and stability issues (like rewriting the results
> processor in the 2.0.7 release) make zero sense when Cuckoo will be
> unusable for any company or person that only uses officially supported
> software (here, Python is the underlying foundation that won't be
supported
> for version 2).
>
> I see Cuckoo up there with projects like Tensorflow, Requests, and
similar
> major players, and they all moved to Python 3 long ago:
> https://python3statement.org/.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#594?email_source=notifications&email_token=AEH6FGG3GJF5J52ICABZ3TTP5UIDNA5CNFSM4BJ6ZT62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFVUPA#issuecomment-508254780
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AEH6FGBXHNLEYOELL4UHVGTP5UIDNANCNFSM4BJ6ZT6Q
>
> .
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#594?email_source=notifications&email_token=ABGVQIUPGAFN7FF7LTRAVF3P5ZTWTA5CNFSM4BJ6ZT62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZIE6KA#issuecomment-508579624>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABGVQIQGM4IJOMXHTCOLY53P5ZTWTANCNFSM4BJ6ZT6Q>
.
|
|
What’s toxic is not informing those of us that depend on this system what the state of development is. I’m super glad that Python 3 is a priority. But not informing us is exactly what causes me to post these kinds of requests. You have to remember that the people that use Cuckoo are not just independent individuals, but entire companies that depend on it (which is where I come from). Though I wish we could support it officially, we don’t have the ability to do so. To that end, that’s why I’m asking if this is still a priority two months after the last comment as made on this post. |
|
I think you have mis-understood things here. I don't think anyone is as you
put it "Toxic" its about having an adult conversation about this. I think
you would also find there are many many people willing to help address the
issues.
On Fri, Jul 5, 2019 at 11:16 AM Wyatt Roersma <[email protected]>
wrote:
… It's being worked on and it's something the cuckoo developers are well
aware of. Making posts like this does little to add to the conversation or
help in any way.
It's actually ultra toxic and doesn't really inspire motivation to spend
free time helping people that can't help themselves.
Even if cuckoo fully supported 3 volatility and many other projects still
don't. I have cuckoo mostly working in python 3 with only a few bugs to
finish out. Though it will only be useful when major libraries it uses also
move to python 3.
On Thu, Jul 4, 2019, 3:30 PM SparkyNZL ***@***.***> wrote:
> Hi Jared,
>
> I dont think you will find much argument here. I too am concerned that
this
> is going to go to the wayside. There are a number of concerning
> vulnerabilities in Cuckoo as it currently stands "Python, and ES" being
> two.
>
> There is nothing stopping people from forking it, but it would require a
> large investment in time to get the architecture under their belt.
>
> Im pretty saddened that its got to this point, ive been a cuckoobox user
> since about 2010 and while i do understand that if you are going to do
this
> full time you need an income, its also important to understand that many
> many people have contributed to the project as well.
>
>
>
> On Thu, Jul 4, 2019 at 9:05 AM Jared M. Smith ***@***.***>
> wrote:
>
> > Where does this issue stand? @LetMeR00t <https://github.com/LetMeR00t>
> > has open PRs on the unsupported libraries. It has been 2 months. We're
> less
> > than 6 months from Python 2 EOL across the board.
> >
> > Cuckoo Sandbox is the *only* open-source, commercially competitive tool
> > for sandboxing; this project needs to stay alive. The only
non-compatible
> > libraries are the ones written by a single GitHub organization (
> > github.com/hatching). Additionally, there isn't a reason to keep
support
> > for Python 2, especially because mitmproxy won't work with it on the
> latest
> > version. Why make it compatible with Python 2, when in 6 months people
> > can't use this software for any project that they're not okay getting
> > wrecked with a Python 2 zero-day.
> >
> > IMO (and I'm sure of many others as well if they realized the full
> > problem), Python 3 should be the *only* priority until its implemented.
> > Non-critical bugs and stability issues (like rewriting the results
> > processor in the 2.0.7 release) make zero sense when Cuckoo will be
> > unusable for any company or person that only uses officially supported
> > software (here, Python is the underlying foundation that won't be
> supported
> > for version 2).
> >
> > I see Cuckoo up there with projects like Tensorflow, Requests, and
> similar
> > major players, and they all moved to Python 3 long ago:
> > https://python3statement.org/.
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <
>
#594?email_source=notifications&email_token=AEH6FGG3GJF5J52ICABZ3TTP5UIDNA5CNFSM4BJ6ZT62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFVUPA#issuecomment-508254780
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/AEH6FGBXHNLEYOELL4UHVGTP5UIDNANCNFSM4BJ6ZT6Q
> >
> > .
> >
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#594?email_source=notifications&email_token=ABGVQIUPGAFN7FF7LTRAVF3P5ZTWTA5CNFSM4BJ6ZT62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZIE6KA#issuecomment-508579624
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ABGVQIQGM4IJOMXHTCOLY53P5ZTWTANCNFSM4BJ6ZT6Q
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#594?email_source=notifications&email_token=AEH6FGDIZ66FGRWX76RRYE3P52AFDA5CNFSM4BJ6ZT62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZIHIKQ#issuecomment-508589098>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEH6FGCMWUN6UZCDACS7FGTP52AFDANCNFSM4BJ6ZT6Q>
.
|
|
@jaredthecoder Disclaimer: I'm not involved in this project. I totally understand your frustration but is very common with any open source projects. You will get a frustrated reply from developers that they are not getting paid and so on. But it was company decision to use this project accepting all risks. So now, since it is important for you, there are multiple options available to make it kicking. You can make an arrangement and donate/pay to authors for this bug to be resolved. You can fork this project and fix it yourself or hire programmers to do it for you. @wroersma You have created something useful during your free time. There is no point replying in toxic way too. Github introduced an interesting initiative https://github.com/sponsors. You might want to think how to get paid for doing what you like. |
|
Hello everybody, as a Debian and Kali packager, I'm super interested in having a python 3 version of cuckoo. Is the python 3 port happening privately or in some public branch? Or is the master branch getting compatible with py2 and py3 at the same time? FWIW, volatility3 is out and supports Python 3: https://github.com/volatilityfoundation/volatility3 |
|
🕙 We are in 2020 and python 2 is deprecated now
Python 2 was dead for years, but now it is officially really dead 😆 |
|
Just dropping a note to say that I was not able to get Cuckoo to work on Ubuntu 20.04 with KVM. I can install and use Cuckoo in Python 2.7, but the current libvirt requires python-libvirt>=6.0.0, which does not support Python 2.7. |
|
Somebody suggested https://github.com/kevoreilly/CAPEv2/ in our tracker |
|
@wroersma - Do you think some of us can be of help in your efforts to getting this to be py3 compatible ? I see that you have said that you have got this mostly working. So wondering if some additional help would be of use to you. Thanks |
|
@benignbala So I have the front end converted to python 3 with a lot of changes here https://github.com/AUCR/cuckoo_plugin the actual python3 version I should release at some point here in a fork of cuckoo https://github.com/AUCR/cuckoo |
|
@wroersma I'd be interested in helping you - if @benignbala would also be up to it even better. |
and others
https://wiki.python.org/moin/Python2orPython3
Support for Python 3.
The text was updated successfully, but these errors were encountered: