- Changed the network adapter setting->Attached to-> "Bridged Adapter" in VirtualBox.
This gave me IP of 192.168.225.26 (found using ip a or ifconfig in the inet field on VM) instead of earlier 10.0.2.15 (when the VM was behind NAT in the above setting).
-
Connected to ariana using
ssh haiji@192.168.225.26from Pavilion. -
Changed password of haiji on ariana (while in
sshfrom Pavilion) withpasswdcommand. -
Watched video for PuTTY, thought I am not using Windows, it was a good watch
-
Not configured ariana with public-key to be used for ssh.
-
I don't think I will ever get a warning like below because I will not be having a public IP with a VirtualBox VM.
Regardless of which client you use, the first time you connect to your server, you may receive a warning that you're connecting to a new server - and be asked if you wish to "cache the host key". Do this. Now, if you get a warning in future connections it means that either: (a) you are being fooled into connecting to a different machine or (b) someone may be trying a "man in the middle" attack.
- Configuring ssh client (Pavilion, in this case?) for fonts and fg/bg colors, PS1, etc.
- What are the chances that the ip (currently, 192.168.225.26) will change in future?
It'll probably stay the same
- How much do I miss out on this course if "the bad guys/bots" are not constantly attacking my server (due to VirtualBox VM) ?
You'll feel a lot safer :-) Seriously though, you can simply do a bunch of SSH attempted logins as "admin" , "root", "test" etc yourself to get some simulated Bad Guy traffic in your logs.
- Why don't we get attacked on cellular mobile data?
Um, your phone won't have any "open ports"?