Commands tagged netcat

This is sneaky.

First, start a listening service on your box.

On the target you will create a new descriptor which is assigned to a network node. Then you will read and write to that descriptor.

You can send it to the background like this:

Now everything you type in our local listening server will get executed on the target and the output of the commands will be piped back to the client.

Receives bzip'd tar archive via netcat (openbsd nc) and stores locally. Displays size with pv. Start this receiver first, then the sender.

Tar's up $DIR locally (w/bzip2) and sends remotely to $HOST:$PORT where netcat listens (using openbsd netcat). Start up receiving side command first, then execute this.

Try to perform a fully TCP 3 way handshake on for a given host-port with a timeout of 1s.

Command makes use of the Malware Hash Registry (http://www.team-cymru.org/Services/MHR/).

It parses the current directory and subdirectories and calculates the md5 hash of the files, then prints the name and sends the hash to the MHR for a lookup in their database.

The 3rd value in the result is the detection percentage across a mix of AV packages.

Very simple web server listening on port 80 will serve index.html file or whatever file you like pointing your browser at http://your-IP-address/index.html for example.

If your web server is down for maintenance and you'd like to inform your visitors about it, quickly and easily, you just have to put into the index.html file the right HTML code and you are done! Of course you need to be root to run the command using port 80.

On the another machine write this command.

pv -r /dev/zero | nc 192.168.1.1 7777

It will show live throughput between two machine.The destination machine ip is at our example 192.168.1.1

You must multiply by 8 for the network calculation.

You must install pv and netcat commands for this commands usage.

kerim@bayner.com

http://www.bayner.com/

Here's a version that uses netcat (although I'd much rather use curl!).

for udp

nmap -sU -p 80 hostname

@putnamhill, no need if statement in that case.

&& is a AND and || is a OR

Requires netcat.

USAGE: gate listening_port host port

Creates listening socket and connects to remote device at host:port. It uses pipes for connection between two sockets. Traffic which goes through pipes is wrote to stdout. I use it for debug network scripts.

Simple one-liner for scanning a range of hosts, you can also scan a range of ports with Netcat by ex.: nc -v -n -z -w 1 192.168.0.1 21-443

Useful when Nmap is not available:)

Range declaration like X..X "for i in {21..29}" is only works with bash 3.0+

sends commands specified in $commandfile to the telnet-server specified by $telnetserver.

to have newlines in $commandfile interpreted as ENTER, save the file in CR+LF (aka "Windows-Textfile") format.

if you want to save the output in a separate file, use:

Pipe whatever you want to this function, it will, if everything goes well, be redirected to a channel or a user on an IRC server.

Please note that :

- I am not responsible of flood excesses you might provoke.

- that function does not reply to PINGs from the server. That's the reason why I first write in a temporary file. Indeed, I don't want to wait for inputs while being connected to the server. However, according to the configuration of the server and the length of your file, you may timeout before finishing.

- Concerning the server, the variable content must be on the form "irc.server.org 6667" (or any other port). If you want to make some tests, you can also create a fake IRC server on "localhost 55555" by using

- Concerning the target, you can choose a channel (beginning with a '#' like "#chan") or a user (like "user")

- The other variables have obvious names.

This is useful for sending data between 2 computers that you have shell access to. Uses tar compression during transfer. Files are compressed & uncompressed automatically. Note the trailing dash on the listening side that makes netcat listen to stdin for data.

on the listening side:

explanation: open netcat to -l listen on -p port 2022, take the data stream and pipe to tar -x extract, -v verbose, -f using file filename - means "stdin"

on the sending side:

explanation: compress all files in current dir using tar -c create, -v verbose, -f using file, - filename - here means "stdout" because we're tar -c instead of tar -x, -w3 wait 3 seconds on stream termination and then end the connection to the listening host name_of_listening_host, on port 2022

To connect to the shell run:

Redirect the local port 2000 to the remote port 3000. The same but UDP:

It may be used to "convert" TCP client to UDP server (or viceversa):