/working/tmp/aruba

[cjbischoff]

Testing/adding to the gauntlt-docker for a Jenkins deployment - when running tests - output details below, but I notice the following ->$ cd /working/tmp/aruba and then a tmp directory is created on the host running the image (no contents)

Whats going on with that? Anyway to control that?

❯❯❯ gauntlt-docker                                                                         
@slow @announce
Feature: simple nmap attack (sanity check)

  Background:                  # ./nmap.attack:3
    Given "nmap" is installed  # gauntlt-1.0.11/lib/gauntlt/attack_adapters/nmap.rb:4
    And the following profile: # gauntlt-1.0.11/lib/gauntlt/attack_adapters/gauntlt.rb:9
      | name      | value           |
      | hostname  | scanme.nmap.org |
      | tcp_ports | 80,443          |

  Scenario: Verify server is available on standard web ports # ./nmap.attack:10
    When I launch an "nmap" attack with:                     # gauntlt-1.0.11/lib/gauntlt/attack_adapters/nmap.rb:8
      $ cd /working/tmp/aruba
      $ nmap -F -PS80,443 scanme.nmap.org
      """
      nmap -F -PS<tcp_ports> <hostname>
      """
    Then the output should match /80.tcp\s+open/             # aruba-0.5.4/lib/aruba/cucumber.rb:171