-
Notifications
You must be signed in to change notification settings - Fork 795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-validate and document OS compatibility #506
Comments
Our test env should include following OS's from AWS:
|
The table should cover server OSes, not desktop, in terms of terminology. Win 2012 and not Win8 |
That's already in the name of AMI's, I added it just for the ease of reference (also IF mokey can exploit server 2003 we can claim that it also exploits XP desktops, because the core is the same, right?). |
For everything except XP and Server 2003, you are correct :) |
I think we also need to cover prior versions of all these OSes, at least major versions |
Windows 2008 R2 |
Yes, monkey works and will continue to work on centos 7+, hrel 7+ and other OS with GLIBC 2.14+. In the future, monkey will exploit, but won't run on older than the mentioned machines. |
@VakarisZ Thanks for the super fast answer. So is there an installation procedure for CentOS 7 / 8? I only find Debian / Ubuntu install script here? https://github.com/guardicore/monkey/tree/develop/deployment_scripts |
If you want development version I'm afraid there aren't any out of the box options, except modifying ubuntu scripts to suit Centos. For production we have built infection monkey for various platforms and you can download it from the official page. |
Is your feature request related to a problem? Please describe.
We currently aren't sure which OSes we support since we upgraded to Python 3.
Describe the solution you'd like
Test which OS versions we currently work on (after upgrading to Python 3 in #394). After documenting which version we don't support, decide on a solution for each one:
Re-test after implementing each solution and update the documentation.
The text was updated successfully, but these errors were encountered: