cloudfuzzer icon indicating copy to clipboard operation
cloudfuzzer copied to clipboard

Results 9 cloudfuzzer issues
Sort by recently updated
recently updated
newest added

When trying run packer build --force -only=virtualbox packer-bastion.json Installation fails and gives: [!!] Select and install software Installation step failed An installation step failed. You can try to run the...

bug

It is possible to setup CloudFuzzer on a group of machines, for example on local VMs, but currently the only way to test the implementation is to deploy CloudFuzzer into...

To avoid long execution time for cloudfuzzer get-results, on remote, we should do periodic get-results on Bastion. One alternative would be to setup a cronjob, for the sync. We also...

help wanted

To prevent us from losing any results when Spot Instances are terminated, we need to detect Termination Notice and trigger result sync. More info about AWS Spot Instance Termination Notice:...

help wanted

We should investigate, if we could create minimalistic implementation to replace [nabeken/docker-volume-container-rsync](https://github.com/nabeken/docker-volume-container-rsync). In addition of dropping external dependency, if the image is built during packer build, we could use the...

help wanted

When stopping instance in gcloud the shutdown script doesn't bring anything to results directory of bastion. Shutdown script is used to rsync result files to bastion when preemptible instance gets...

After Docker upgrade, old docker swarm control scripts went obsolete, and were removed. run-containers.sh creates N fuzzing containers as a service named "fuzz-service". Adding rest of the docker service commands...

Documentation should be improved to be more readable

enhancement