1SC_TBITBLIND(1)           BSD General Commands Manual          SC_TBITBLIND(1)
2

NAME

4     sc_tbitblind — scamper driver to test systems for resilience to blind TCP
5     attacks.
6

SYNOPSIS

8     sc_tbitblind [-r] [-a addressfile] [-A application] [-c completed-file]
9                  [-l limit-per-file] [-o output-file] [-O options]
10                  [-p scamper-port] [-t log-file] [-T ttl] [-w wait-between]
11

DESCRIPTION

13     The sc_tbitblind utility provides the ability to connect to a running
14     scamper(1) instance and use that instance to test systems for resilience
15     to blind TCP attacks, with the output written to a file in warts format.
16     The utility tests a given system for regular TCP behavior, and then tests
17     the system for response to reset, SYN, and data packets that could have
18     come from a blind attacker because the sequence number is not the next
19     sequence number value expected by the receiver (the reset and SYN cases)
20     or the acknowledgment value covers data ahead or behind the receiver's
21     point in their sequence number space (the data cases).  The utility also
22     tests the system's response to a connection that advertises support for
23     window scaling, TCP timestamps, and Selective Acknowledgments (SACK).
24
25     The options are as follows:
26
27     -?      prints a list of command line options and a synopsis of each.
28
29     -a addressfile
30             specifies the name of the input file which constists of a
31             sequence of systems to test, one system per line.
32
33     -A application
34             specifies the type of application to simulate while testing the
35             system.  Options are HTTP and BGP.
36
37     -c completed-file
38             specifies the name of a file to record IP addresses that have
39             been tested.
40
41     -l limit-per-file
42             specifies the number of tbit objects to record per warts file,
43             before opening a new file and placing new objects.
44
45     -o output-file
46             specifies the name of the file to be written.  The output file
47             will use the warts format.
48
49     -O options
50             allows the behavior of sc_tbitblind to be further tailored.  The
51             current choices for this option are:
52               -  noshuffle: do not shuffle the order of the input list or the
53                  order of the tests.
54
55     -p scamper-port
56             specifies the port on the local host where scamper(1) is accept‐
57             ing control socket connections.
58
59     -r      causes the random number generator used to shuffle tests be
60             seeded.
61
62     -t log-file
63             specifies the name of a file to log progress output from
64             sc_tbitblind generated at run time.
65
66     -T ttl  specifies the IP-TTL to use with the blind TCP tests.
67
68     -w wait-between
69             specifies the length of time to wait between any two TCP tests to
70             one system.
71

EXAMPLES

73     Use of this driver requires a scamper instance listening on a port for
74     commands, which has been configured to use the IPFW firewall as follows:
75
76           scamper -P 31337 -F ipfw
77
78     To test a set of web servers specified in a file named webservers.txt and
79     formatted as follows:
80
81        1,example.com 1263 192.0.2.1 http://www.example.com/
82        1,example.com 1263 2001:DB8::1 http://www.example.com/
83        1,example.com 1263 2001:DB8::2 https://www.example.com/
84
85     the following command will test all servers for resilience to blind TCP
86     attacks and record raw data into webservers_00.warts, web‐
87     servers_01.warts, etc:
88
89           sc_tbitblind -a webservers.txt -p 31337 -o webservers
90
91     The webservers.txt file is required to be formatted as above.  The format
92     is: numeric ID to pass to tbit, a label for the webserver, the size of
93     the object to be fetched, the IP address to contact, and the URL to use.
94
95     To test a set of BGP routers specified in bgprouters.txt and formatted as
96     follows:
97
98        192.0.2.2 65000
99        192.0.2.2 65001
100
101     the following command will test all BGP routers for resilience to blind
102     TCP attacks, without shuffling the test order, waiting 180 seconds
103     between tests, and record raw data into bgprouters_00.warts,
104     bgprouters_01.warts, etc:
105
106           sc_tbitblind -a bgprouters.txt -p 31337 -o bgprouters -A bgp -O
107           noshuffle -w 180
108
109     The bgprouters.txt file is required to be formatted as above.  The format
110     of that file is: IP address to establish a BGP session with, and the ASN
111     to use.
112

SEE ALSO

114     M. Luckie, R. Beverly, T. Wu, M. Allman, and k. claffy, Resilience of
115     Deployed TCP to Blind Attacks, Proc. ACM/SIGCOMM Internet Measurement
116     Conference 2015.  scamper(1), sc_wartsdump(1), sc_warts2json(1), warts(5)
117

AUTHORS

119     sc_tbitblind was written by Matthew Luckie <mjl@luckie.org.nz>.  Tiange
120     Wu contributed an initial implementation of the blind in-window TBIT test
121     to scamper, and Robert Beverly contributed support for testing BGP
122     routers.
123
124BSD                           September 19, 2015                           BSD
Impressum