Skip to content
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

Closed
ShayNehmad opened this issue Dec 4, 2019 · 11 comments
Closed

Re-validate and document OS compatibility #506

ShayNehmad opened this issue Dec 4, 2019 · 11 comments
Assignees
Labels
Documentation Issues relating to the project's documentation like readme files, guides, etc.
Milestone

Comments

@ShayNehmad
Copy link
Contributor

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:

  • Ignore since the OS is too old for us to care about anyway (yes Ubuntu 8, I'm looking at you).
  • Write a bootloader (in C++ or something) which reports back to the Island that this machine is too old for the regular Monkey to operate. Mark super-old machines in the Island as fatal security flaws. See Create monkey bootloader for obsolete systems  #479.
  • Create compatibility, using solutions like staticx.

Re-test after implementing each solution and update the documentation.

@ShayNehmad ShayNehmad added Monkey Documentation Issues relating to the project's documentation like readme files, guides, etc. labels Dec 4, 2019
@ShayNehmad ShayNehmad added this to the 1.8.0 milestone Dec 4, 2019
@VakarisZ
Copy link
Contributor

VakarisZ commented Dec 5, 2019

Our test env should include following OS's from AWS:

Added? OS AMI Bits
Windows XP Racemi-Windows_Server-2003-R2_SP2-English-32Bit-Base-2015.12.31 - ami-01e4fa6d 32
Windows vista Microsoft Windows Server 2008 R2 Base - ami-0f41c4b97d72ae2b7 64
Windows vista Windows_Server-2008-SP2-English-64Bit-Base-2019.08.16 - ami-0252def122d07efd3 64
Windows 8 Microsoft Windows Server 2012 Base - ami-0d8c60e4d3ca36ed6 64
Windows 8 Microsoft Windows Server 2012 R2 Base - ami-08dcceb529e70f875 64
Windows 10 Microsoft Windows Server 2019 Base - ami-09fe2745618d2af42 64
Ubuntu 12.04 ubuntu/images/hvm/ubuntu-precise-12.04-amd64-server-20120424 - ami-003d0b1d 64
Ubuntu 14.04 Ubuntu Server 14.04 LTS (HVM), SSD Volume Type - ami-067ee10914e74ffee 64
Ubuntu 19.04 ubuntu/images-testing/hvm-ssd/ubuntu-disco-daily-amd64-server-20190702 - ami-001b87954b72ea3ac 64
CentOS-7 CentOS 7 (x86_64) - with Updates HVM 64
RHEL 7.2 Red Hat Enterprise Linux (RHEL) 7.2 (HVM) 64
Kali 2019.3 Kali Linux 2019.3-8b7fdfe3-8cd5-43cc-8e5e-4e0e7f4139d5-ami-0327257c586faca43.4 - ami-05d64b1d0f967d4bf 64
SUSE 12 SUSE Linux Enterprise Server 12 SP4 (HVM), SSD Volume Type - ami-07b12b913a7e36b08 64

@danielguardicore
Copy link
Contributor

The table should cover server OSes, not desktop, in terms of terminology. Win 2012 and not Win8

@VakarisZ
Copy link
Contributor

VakarisZ commented Dec 5, 2019

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?).

@danielguardicore
Copy link
Contributor

For everything except XP and Server 2003, you are correct :)
Specifically, XP and Server 2003 are old enough to be different kernel versions.

@danielguardicore
Copy link
Contributor

I think we also need to cover prior versions of all these OSes, at least major versions

@danielguardicore
Copy link
Contributor

Windows 2008 R2
Windows 2012
Windows 2012 R2
Windows 2016
Ubuntu 12.04
Ubuntu 14.04
Ubuntu 16.04
Ubuntu 18.04
Debian 7
Debian 8
Debian 9
Centos 6
Centos 7
RHEL 5
RHEL 6
RHEL 7
Oracle Linux 6
Oracle Linux 7
Suse 11
Suse 12

@willemdh
Copy link

Hello, Do I understand correctly that Infection monkey is compatible with CentOS 7 too?

The setup page only shows:

image

But we only use CentOS / Red Hat at work so it would be supercool if I could get it to work on CentOS... :)

@VakarisZ
Copy link
Contributor

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.

@willemdh
Copy link

@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

@VakarisZ
Copy link
Contributor

VakarisZ commented Feb 18, 2020

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.

@VakarisZ
Copy link
Contributor

Updated: https://github.com/guardicore/monkey/wiki/OS-compatibility

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Issues relating to the project's documentation like readme files, guides, etc.
Projects
None yet
Development

No branches or pull requests

4 participants