Please answer following short questions for thumbs up:- a) What is the only the
ID: 3904405 • Letter: P
Question
Please answer following short questions for thumbs up:-
a) What is the only the client platforms that you can use Putty to access Kali Linux server? Where can you use Windows to access Kali Linux Server?
b) How are dynamic, private IP addresses assigned when using RMU VMware Horizon View?
c) Assume that you logon to a RMU VMware Horizon client on Saturday and then re-logon to RMU VMware Horizon View on Sunday. The assigned IP address will change. Which Windows commands may you use to find the current private IP address assigning to your host.
d) What is the difference between a public IP address or network and a Private IP address or network that is used by RMU VMware Horizon client?
e) Explain the process and network devices that will restrict RMU private network to communicate to our RMU AWS private network, but your RMU AWS Kali cannot communicate any other networks.
f) Assume that you have been assigned ec2-54-235-229-171.compute-1.amazonaws.com as your AWS host name. When you ping or use Putty to ec2-54-235-229-171.compute-1.amazonaws.com, which network protocol is used to convert a host name into a private IP address?
Explanation / Answer
(Only 3 questions will be answered as per the rule)
a) Linux(Ubuntu) is the only client that is use to access Kali Linux server.
While this setup of Kali on Windows is not optimal due to various environmental restrictions (such as the lack of raw sockets and lack of customised Kali kernel), there are still many situations where having Kali Linux alongside your Windows 10 machine can be beneficial. One example that comes to mind is consolidation of workspaces, especially if Windows is your main working environment. Other useful situations that crossed our minds were standardizing tools and scripts to run across multiple environments, quick porting of Linux penetration testing command line tools to Windows, etc.
Steps to set it up in Windows:
1. Update your Windows 10 machine. Open an administrative PowerShell window and install the Windows Subsystem with this one-liner. A reboot will be required once finished.
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
2. Once rebooted, open a command line shell and run the following commands to install the default Ubuntu environment. This will lay down the foundations for our Kali install.
lxrun /install
3. Setup and install the WSL Switcher, download a Kali base, and extract it to disk:
git clone https://github.com/RoliSoft/WSL-Distribution-Switcher.git
cd WSL-Distribution-Switcher
python get-prebuilt.py kalilinux/kali-linux-docker
python install.py rootfs_kalilinux_kali-linux-docker_latest.tar.gz
lxrun /setdefaultuser root
b)
Choosing the Method for Assigning IP Addresses
For virtual machines that you do not expect to keep for long, use DHCP and let it allocate an IP address.
For each host-only or NAT network, the available IP addresses are split up using the conventions shown in the tables below, where <net> is the network number assigned to your host-only or NAT network. VMware Workstation always uses a Class C address for host-only and NAT networks.
Range
Address use
Example
<net>.1
Host machine
192.168.0.1
<net>.2-<net>.127
Static addresses
192.168.0.2-192.168.0.127
<net>.128-<net>.253
DHCP-assigned
192.168.0.128-192.168.0.253
<net>.254
DHCP server
192.168.0.254
<net>.255
Broadcasting
192.168.0.255
Address Use on a NAT Network
Range
Address use
Example
<net>.1
Host machine
192.168.0.1
<net>.2
NAT device
192.168.0.2
<net>.3-<net>.127
Static addresses
192.168.0.3-192.168.0.127
<net>.128-<net>.253
DHCP-assigned
192.168.0.128-192.168.0.253
<net>.254
DHCP server
192.168.0.254
<net>.255
Broadcasting
192.168.0.255
c) Found under
HKEY_CURRENT_USERVolatile Environment
Here is an example of how it can be used. Values on the guest VM should be as follows:
HKLMSoftwarePoliciesVMware, Inc.Vmware VDMAgentConfigurationCommandsToRunOnConnect
Command1=“wscript.exe c: econnectscript.vbs”
HKLMSoftwarePoliciesVMware, Inc.VMware VDMAgentConfigurationCommandsToRunOnReconnect
Command1=“wscript.exe c: econnectscript.vbs”
Then write the script to look something like the following. The below will pop the information up in a small window:
————————————————-
Begin Script
————————————————-
Const HKEY_CURRENT_USER = &H80000001
Set wmiLocator=CreateObject(“WbemScripting.SWbemLocator”)
Set wmiNameSpace = wmiLocator.ConnectServer(“.”, “rootdefault”)
Set objRegistry = wmiNameSpace.Get(“StdRegProv”)
sPath = “Volatile Environment”
lRC = objRegistry.GetStringValue(HKEY_CURRENT_USER, sPath, “ViewClient_Machine_Name”, vMachine)
lRC = objRegistry.GetStringValue(HKEY_CURRENT_USER, sPath, “ViewClient_IP_Address”, vIP)
lRC = objRegistry.GetStringValue(HKEY_CURRENT_USER, sPath, “ViewClient_MAC_Address”, vMAC)
msgbox “The Remote Device Name is ” & vMachine & ” @ ” & vIP & ” (” & vMAC & “) ”
————————————————-
End Script
————————————————-
?
Range
Address use
Example
<net>.1
Host machine
192.168.0.1
<net>.2-<net>.127
Static addresses
192.168.0.2-192.168.0.127
<net>.128-<net>.253
DHCP-assigned
192.168.0.128-192.168.0.253
<net>.254
DHCP server
192.168.0.254
<net>.255
Broadcasting
192.168.0.255