forwarder a raw socket proxy with optional SSL/TLS termination and trace capability
With this tool you can intercept communication between a server an a client. Its
specially handy for tracing/debugging communication from a client to server, reverse
engineering a protocol stack.
For your own Python script with minor change the traffic is routed to forwarder.
This can also be an external application assuming that you can alter the communication
parameters of the application.
It can optionally also perform the SSL/TLS termination to the server, so that
the communication to the client is in clear text.
It can handle multiple sessions, multiple servers ans ports at the same time.
At this moment TCP sessions are fully supported (stable).
At this moment UDP messages is supported (unstable)
Installation
PIP
> pip install forwarder
from source
> git clone https://github.com/pe2mbs/pyforwarder.git
> cd pyforwarder
> pip install .
Package version
The version of the package is as follows: x.y.z
Where x is the major version number
Where y is the minor version number
Where z is the build number
Basic operation
The basic operation is simple start the forwarder with a configuration file.
> pyforwarder config-example.yaml
NOTE that the startup script is called pyforwarder.
Depending on the settings it shows the program banner and optionally verbose
and trace information what is happing.
Usage
There are two types of usages.
- raw socket with an exact configuration in the configuration file.
- proxy socket where the configuration is passed on over the initial socket
raw socket
For each destination there must be and complete config uration with address,
port and optional SSL/TLS parameters for the destination and for the source
the address and port where pyforwarder listens on.
proxy socket
For proxy socket in the configuration the source address and port must be defined
where pyforwarder listens on. And for the destination the proxy must be enabled
with optional the username and password (these are send in encoded over the session).
The proxy handshake is simple the server says HELO and the client respond
with OLEH
the forwarder.csocket module contains a class TcpSocket where this mechanism is
implemented. it also declares socket. for easy replacement of the import socket
import forwarder.csocket as socket
By using this traffic on hat socket will be routed to the forwarder.
See for more information the test script testproxy.py.
If you need all traffic from you application routed through the forwarder proxy,
you can import forwarder.hook
in the main file of your project, and all sessions
will be routed through the forwarder proxy.
See for more information the test script hookproxy.py
NOTE: proxy socket works only for TCP sessions.
Configuration
The configuration file can be a YAML or JSON formatted file. The example below
shows the YAML format.
version: 2
options:
trace: true
hexdump: true
verbose: true
logging:
version: 1
formatters:
trace:
class: logging.Formatter
format: '%(asctime)s %(levelname)-8s %(message)s'
verbose:
class: logging.Formatter
format: '%(asctime)s %(message)s'
handlers:
console:
class: logging.StreamHandler
level: DEBUG
formatter: verbose
stream: ext://sys.stdout
file:
level: DEBUG
class: logging.FileHandler
encoding: utf-8
filename: tracefile.log
mode: w
formatter: trace
root:
level: DEBUG
handlers:
- console
- file
ports:
dynamic-proxy:
port: 18080
protocol: tcp
description: dynamic proxy using the TcpSocket() from psocket
hosts:
- source:
addr: 0.0.0.0
port: 8008
destination:
addr: 192.168.123.5
port: imaps
use-ssl-tls: true
ssl-tls:
verify: false
check-host: false
required: optional
- source:
port: 8009
destination:
addr: 192.168.123.5
port: smtps
use-ssl-tls: false
ssl-tls:
verify: false
check-host: false
required: optional
- source:
addr: localhost
port: 8010
destination:
addr: 192.168.123.6
port: 25057
use-ssl-tls: false
enabled: false
- source:
addr: 192.168.123.100
port: 18080
destination:
proxy: true
username: guest
password: guest
version
The version
at root level must be 2 at this time.
options
The options
at root level can also be set via the command line, but the
settings in the configuration file are always leading.
logging
The logging
at root level defines how the application does its logging.
When this is omitted the default is as defined in the example above. When
you want greater detail on the console just change the level
in
logging.handlers.console
to DEBUG then the same detail as in the log
file is shown on the console.
hosts
The hosts
is a list of host source/destination configuration items.
Each list item constists out of the following items;
source
destination
enabled
is a flag (true/false) of the host configuration is active,
when omitted the default is true.
source
The source
has two attributes;
addr
: the address to listen on, when omitted the 0.0.0.0 address shall be
used therefore the the listen is on all network adaptors.port
: the port to listen on.
destination
The destination
has two attributes;
addr
: the address to connect to when an incomming connection is established
on the source.port
: the port to to connect to.use-ssl-tls
: is a flag (true/false) whether the SSL/TLS termination is
enabled for the session. When enabled the ssl-tls
attributes
will be used to set extra SSL/TLS parameters.ssl-tls
this may contain the following attributes verify
, check-host
,
required
, ca-bundle
, certificate
and key
.
verify
With verify
the certicate verifcation can be enabled or disabled, the default
is true
check-host
With check-host
the host name verifcation can be enabled or disabled, the
default is true
required
With required
the host certicate can be required, optional or none. The values
- true: required
- false: none
- optional: optional
ca-bundle
The ca-bundle
is the filename to the CA bundle with the certicates: CA and client.
certificate
The certificate
is the filename to the client certicate.
key
The key
is the filename to the client private key file.
ports
The ports
is a dictionary of port defintions. This is an optional attrbute and
is an addition to the predefined ports. Each entry constist out of a unique
protocol name with the following attributes;
- port: the port number
- description: the description of the protcol
- protocol: may be set to TCP and/or UDP, when both need to be set the list syntax
is used.
See section predefined ports
Tests
For the following test scripts, pyforwarder must be started with the following configuration
items in the config file.
ports:
raw-proxy:
port: 18080
protocol: tcp
description: TCP raw proxy
hosts:
- source:
addr: localhost
port: raw-proxy
destination:
proxy: true
username: guest
password: guest
testproxy.py
import forwarder.psocket as socket
proxyConfig = dict( proxy = ( "localhost", 18080 ),
username = 'guest',
password = 'guest' )
sock = socket.socket()
sock.connect( ( "smtp.gmail.com", 25 ), **proxyConfig )
data = sock.recv(1024)
print( data )
sock.close()
print( "Done" )
hookproxy.py
import forwarder.hook
import socket
import requests
forwarder.hook.proxyConfig = dict( proxy = ( "localhost", 18080 ),
username = 'guest',
password = 'guest' )
sock = socket.socket()
sock.connect( ( "smtp.gmail.com", 25 ) )
data = sock.recv(1024)
print( data )
sock.close()
result = requests.get( "http://google.nl" )
print( result.content.decode( 'utf-8' ) )
result = requests.get( "https://google.nl" )
print( result.content.decode( 'utf-8' ) )
print( "Done" )
Predefined ports
The predefined ports:
ftp:
port: 20
description: file transfer protocol
protocol: tcp
ftpc:
port: 21
description: file transfer protocol control
protocol: tcp
ssh:
port: 22
description: Secure Shell
protocol: tcp
telnet:
port: 23
description: Telnet", "protocol": "tcp" },
smtp:
port: 25
description: Simple Mail Transfer Protocol, verzending van e-mail (MTA)
protocol: tcp
dns:
port: 53
description: Domain Name System
protocol: udp
dhcpc:
port: 67
description: Domain Name System client
protocol: udp
dhcps:
port: 68
description: Domain Name System server
protocol: udp
tftp:
port: 69
description: Trivial File Transfer Protocol
protocol: udp
http:
port: 80
description: Hypertext Transfer Protocol
protocol:
- tcp
- udp
pop3:
port: 110
description: Post Office Protocol 3, receive of e-mail
protocol: tcp
nntp:
port: 119
description: Network News Transfer Protocol
protocol: tcp
ntp:
port: 123
description: Network Time Protocol
protocol: tcp
netbns:
port: 137
description: NetBIOS Name Service
protocol: udp
netbds:
port: 138
description: NetBIOS Name Service
protocol: udp
netbss:
port: 139
description: NetBIOS Session Service
protocol: tcp
imap:
port: 143
description: Internet Message Access Protocol
protocol: tcp
snmp:
port: 161
description: Simple Network Management Protocol
protocol: udp
snmptrap:
port: 162
description: Simple Network Management Protocol, getriggerde notificaties
protocol: udp
ldap:
port: 389
description: Lightweight Directory Access Protocol
protocol: tcp
https:
port: 443
description: HyperText Transfer Protocol over TLS/SSL
protocol: tcp
smb:
port: 445
description: Direct Hosting / SMB (Samba) over TCP
protocol: tcp
smtps-alt:
port: 465
description: Simple Mail Transfer Protocol over TLS/SSL
protocol: tcp
dhcpc-alt:
port: 546
description: Domain Name System (ipv6) client
protocol: udp
dhcps-alt:
port: 547
description: Domain Name System (ipv6) server
protocol: udp
msn:
port: 569
description: Multiple Subscriber Number
protocol: tcp
smtps:
port: 587
description: Simple Mail Transfer Protocol, verzending van uitgaande e-mail (MSA)[16]
protocol: tcp
ftps:
port: 990
description: File Transfer Protocol over SSL
protocol: tcp
imaps:
port: 993
description: Internet Message Access Protocol over TLS/SSL
protocol: tcp
pop3s:
port: 995
description: Post Office Protocol 3, ontvangen van e-mail over TLS/SSL
protocol: tcp
socks:
port: 1080
description: SOCKS proxy
protocol: tcp
openvpn:
port: 1194
description: OpenVPN
protocol:
- tcp
- udp
mysql:
port: 3306
description: MySQL databasesysteem
protocol:
- tcp
- udp
rdp:
port: 3389
description: Remote Desktop Protocol
protocol: tcp
daap:
port: 3689
description: Digital Audio Access Protocol
protocol: tcp
postgresql:
port: 5432
description: PostgreSQL databasesysteem
protocol:
- tcp
- udp
vnc:
port: 5800
description: Virtual Network Computing
protocol: tcp
vnc-alt:
port: 5900
description: Virtual Network Computing
protocol: tcp
gp2p:
port: 5900
description: Gnutella p2p netwerk
protocol: tcp
http-alt:
port: 8080
description: WWW caching service proxyservers and Apache Tomcat
protocol: tcp