Blog: 2023-08-11: Difference between revisions

From razwiki
Jump to navigation Jump to search
(Created page with "I got vagrant running on wsl using virtualbox as a provider - the problem was my firewall https://github.com/Karandash8/virtualbox_WSL2/issues/1 Disabling the firewall entire...")
 
No edit summary
Line 8: Line 8:


Once I opened that, I noticed the commit referenced `git-ubuntu import`. Not sure what this is, and hard to google
Once I opened that, I noticed the commit referenced `git-ubuntu import`. Not sure what this is, and hard to google

Ok much hacking later, working on getting a ronin box going. While waiting for a machine, remembered THC root machines, and tried to ssh:


It prompts for a password, which is simply "segfault", but I don't want to type that. Googling around gave this great pexpect script https://serverfault.com/a/241589/311519

<pre>
#!/usr/bin/expect -f
# ./ssh.exp password 192.168.1.11 id
set pass [lrange $argv 0 0]
set server [lrange $argv 1 1]
set name [lrange $argv 2 2]

spawn ssh $name@$server
match_max 100000
expect "*?assword:*"
send -- "$pass\r"
send -- "\r"
interact
</pre>

Works great!

Revision as of 02:39, 11 August 2023

I got vagrant running on wsl using virtualbox as a provider - the problem was my firewall https://github.com/Karandash8/virtualbox_WSL2/issues/1

Disabling the firewall entirely worked, so then I figured I'd try the powershell script to only modify the virtualbox one. but then I got an error about vagrant versions differing on windows and wsl, which is weird to me since I imagine it shouldn't matter which side has which virtualbox version.

I briefly looked into bumping the version of vagrant that ubuntu has, and got as far as cloning the ubuntu packaging repository:

git clone https://git.launchpad.net/ubuntu/+source/vagrant ubuntu-vagrant

Once I opened that, I noticed the commit referenced `git-ubuntu import`. Not sure what this is, and hard to google

Ok much hacking later, working on getting a ronin box going. While waiting for a machine, remembered THC root machines, and tried to ssh:

ssh [email protected]

It prompts for a password, which is simply "segfault", but I don't want to type that. Googling around gave this great pexpect script https://serverfault.com/a/241589/311519

#!/usr/bin/expect -f
#  ./ssh.exp password 192.168.1.11 id
set pass [lrange $argv 0 0]
set server [lrange $argv 1 1]
set name [lrange $argv 2 2]

spawn ssh $name@$server
match_max 100000
expect "*?assword:*"
send -- "$pass\r"
send -- "\r"
interact

Works great!