Cryptcat can be used as an alternative to ssh when you just want to hide your data from potential packet sniffers on the network and are not too worried about other aspects of security.
The main difference between Cryptcat and Netcat as far as usage is concerned, is that you must supply a password to. It takes this password and uses it as a salt to encrypt the data being sent.
Be sure to supply a password to cryptcat, otherwise the connection will be encrypted using the default which everyone will obviously have access to.
Note that as with our Netcat examples, the port numbers used are arbitrary. Only the super user can use port numbers below 1024. Also check that the ports are not being blocked by your firewall.
connect to somewhere: nc [-options] hostname port[s] [ports] …
listen for inbound: nc -l -p port [-options] [hostname] [port]
-g gateway source-routing hop point[s], up to 8 -G num source-routing pointer: 4, 8, 12, ... -h this cruft -i secs delay interval for lines sent, ports scanned -l listen mode, for inbound connects -n numeric-only IP addresses, no DNS -o file hex dump of traffic -p port local port number -r randomize local and remote ports -s addr local source address -u UDP mode -v verbose [use twice to be more verbose] -w secs timeout for connects and final net reads -z zero-I/O mode [used for scanning] port numbers can be individual or ranges: lo-hi [inclusive]
Basic Chat Server with Encryption
On the server side, set up to listen for connections on port 3333
cryptcat -k mysecretkey -l -p 3333
On the client side connect using:
cryptcat -k mysecretkey <server-ip-address> 3333 //same as of server key
e.g. on server :
cyborg@cyborg:~$ cryptcat -k a#%c1x512s$$ -l -p 3333 hi how are you
On Client :
cyborg@cyborg:~$ cryptcat -k a#%c1x512s$$ 192.168.1.12 3333 hi how are you ^C punt!