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

Purpose #1

Closed
freb opened this issue Aug 8, 2019 · 2 comments
Closed

Purpose #1

freb opened this issue Aug 8, 2019 · 2 comments

Comments

@freb
Copy link
Collaborator

freb commented Aug 8, 2019

It should be like https://github.com/tomsteele/cloud-proxy only for running commands across all the cloud instances. The main use case is to distribute an nmap scan accross many cloud instances so that we can scan slower and not get blocked.

features:

  • break ports up into even sized random chunks.
  • pass a second command to check if we've been black listed or not (possibly multiple commands). This will usually take the form of check if this port is showing open. Somtimes you're blacklisted if a port that should be closed is showing open (because all ports are showing open to confuse the scanner) and sometimes you are blacklisted if a port that should be open is showing closed (because they've blocked you completely)
@freb freb pinned this issue Aug 8, 2019
@freb
Copy link
Collaborator Author

freb commented Aug 8, 2019

It would be nice to not have nmap be a special case.

We want to launch instances and have then continue to run, but we want to be able to do more than just run something right at the start. We need a way to be able to lanch commands and monitor their progress. That is probably more complicated than initially intended, but it would be very nice.

You could have each command be a function of the input, with a variable for each host which is its number (1-total number of droplets). That way you could do some breaking up of a master command so that each host does its part. This is supported with csrange to split the ports up into buckets and then select a specific bucket (which could be done by instance #).

Another option is to paste in a crap ton of commands and it'll treat each line like its own command and send them off to the instances in turn. So if you issue 4 commands it'll send them to the first 4 instances.

I would like to be able to issue a single command and have it do what is right though, but that would be more difficult.

@freb
Copy link
Collaborator Author

freb commented Aug 11, 2019

Most of this is covered in the README. Closing.

@freb freb closed this as completed Aug 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant