Not seeing additional target VMs about pentest-env HOT 8 CLOSED

Hi,

You should have your .pentestrc and .pentest.d setup in your windows host machine, not in the kali instance.
Here I see you have setup pentest-env in the kali vm, and want use it in your windows host. So vagrant on your host machine cannot read your setup and use the default configuration instead, that's why you have not your additional target.

Try using a pentestrc in your windows machine, I'm not sure it works out of the box with windows host because I have never tested this OS. In case it's not working, keep me updated I will look to add compatibility, you can also send a pull request :)

from pentest-env.

Trying to skip two lines because of possible OS issue, from my little knowledge of Ruby, I don't have to specify the target path because it'll default in the target.rb line 39. So would this work?

Yea I'm still having trouble after I've moved the file is on the host side.

from pentest-env.

Yes, just move .pentestrc in your home: ~/.pentestrc it should works

from pentest-env.

We're getting closer! haha

from pentest-env.

You missed comma in your array of target:

targets: [dvwa, metasploitable, primer]

or

targets: 
  - dvwa
  - metasploitable
  - primer

This is YaML syntax.

About t.chomp: http://ruby-doc.org/core-2.3.0/String.html#method-i-chomp
It ensure there is no unwanted newline in the target name

from pentest-env.

P.S. Please stop posting image, copy/past backtraces/errors/debug instead. Thx

from pentest-env.

I GOT IT.

I broke it when I was tindering with the ruby code, then when I moved .pentestrc to host machine home root it wasn't working until I reverted everything.

I think I initially got hung up on the Customizations page, since you showed linux commands I assumed you were referring to guest machine since I'm on Windows

Thanks for all your help and sorry to be a bother on my mistake.

from pentest-env.

No problem, happy to see you resolved your issue :)

from pentest-env.