search

SamuraiWTF / samuraiwtf

The main SamuraiWTF collaborative distro repo.
https://owasp.org/www-project-samuraiwtf/#SamuraiWTF_Project
GNU Lesser General Public License v3.0
462 stars 119 forks source link

Login credentials not working #81

Closed bkimminich closed 5 years ago

bkimminich commented 5 years ago

Running SamuraiWTF 4.1.1 on Vagrant on Windows seemingly successfully:

Bringing machine 'samuraiwtf' up with 'virtualbox' provider...
==> samuraiwtf: Checking if box 'bento/debian-9' version '201812.27.0' is up to date...
==> samuraiwtf: Clearing any previously set forwarded ports...
==> samuraiwtf: Clearing any previously set network interfaces...
==> samuraiwtf: Preparing network interfaces based on configuration...
    samuraiwtf: Adapter 1: nat
==> samuraiwtf: Forwarding ports...
    samuraiwtf: 22 (guest) => 2222 (host) (adapter 1)
==> samuraiwtf: Running 'pre-boot' VM customizations...
==> samuraiwtf: Booting VM...
==> samuraiwtf: Waiting for machine to boot. This may take a few minutes...
    samuraiwtf: SSH address: 127.0.0.1:2222
    samuraiwtf: SSH username: vagrant
    samuraiwtf: SSH auth method: private key
==> samuraiwtf: Machine booted and ready!
==> samuraiwtf: Checking for guest additions in VM...
==> samuraiwtf: Setting hostname...
==> samuraiwtf: Mounting shared folders...
    samuraiwtf: /vagrant => C:/Data/GitHub/samuraiwtf
    samuraiwtf: /tmp/config => C:/Data/GitHub/samuraiwtf/config
==> samuraiwtf: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> samuraiwtf: flag to force provisioning. Provisioners marked to run always will still run.

But I then cannot log in with samurai/samurai: image

mgillam commented 5 years ago

@bkimminich thanks for the issue. Attempting to duplicate. It looks like this was a vagrant up on an already provisioned instance. Is there anything you can think of that might have interrupted the provisioning?

mgillam commented 5 years ago

I just freshly provisioned an instance an it worked initially. Do you recall what you did? vagrant up then vagrant down then vagrant up again? And this is 4.1.1 from Master, correct?

bkimminich commented 5 years ago

I did vagrant halt in between. I'll destroy the machine and start from scratch to see if anything disturbed provisioning.

bkimminich commented 5 years ago

image

Is that normal that the login box already shows up while provisioning is still ongoing... I guess I'll wait until all is done, restart the box and then try logging in for the first time. Let's see how that plays out...

secureideas commented 5 years ago

Yes it is normal. We have looked to see how to hide it, but the base box is running so the log in appears. I have done this exact thing multiple times and I know that vagrant does it. :)

bkimminich commented 5 years ago

Ok, now it works. "Patience" was the solution... :-D