| 1 | .TH TRACEANON "1" "October 2005" "traceanon (libtrace)" "User Commands" |
|---|
| 2 | .SH NAME |
|---|
| 3 | traceanon \- anonymise ip addresses of traces |
|---|
| 4 | .SH SYNOPSIS |
|---|
| 5 | .B traceanon |
|---|
| 6 | [ \-s | \-\^\-encrypt-source ] |
|---|
| 7 | [ \-d | \-\^\-encrypt-dest ] |
|---|
| 8 | [ \-p prefix | \-\^\-prefix=prefix ] |
|---|
| 9 | [ \-c key | \-\^\-cryptopan=key ] |
|---|
| 10 | sourceuri |
|---|
| 11 | desturi |
|---|
| 12 | .SH DESCRPTION |
|---|
| 13 | traceanon anonymises a trace by replacing IP addresses found in the IP header, |
|---|
| 14 | and any embedded packets inside an ICMP packet. It also fixes the checksums |
|---|
| 15 | inside TCP and UDP headers. |
|---|
| 16 | |
|---|
| 17 | Two anonymisation schemes are supported, the first replaces a prefix with |
|---|
| 18 | another prefix. This can be used for instance to replace a /16 with the |
|---|
| 19 | equivilent prefix from RFC1918. The other scheme is cryptopan which is a |
|---|
| 20 | prefix preserving encryption scheme based on AES. |
|---|
| 21 | .TP |
|---|
| 22 | .PD 0 |
|---|
| 23 | .BI \-s |
|---|
| 24 | .TP |
|---|
| 25 | .PD |
|---|
| 26 | .BI \-\^\-encrypt-source |
|---|
| 27 | encrypt only source ip addresses. |
|---|
| 28 | |
|---|
| 29 | .TP |
|---|
| 30 | .PD 0 |
|---|
| 31 | .BI \-d |
|---|
| 32 | .TP |
|---|
| 33 | .PD |
|---|
| 34 | .BI \-\^\-encrypt-dest |
|---|
| 35 | encrypt only destination ip addresses. |
|---|
| 36 | |
|---|
| 37 | .TP |
|---|
| 38 | .PD 0 |
|---|
| 39 | .BI \-p |
|---|
| 40 | .TP |
|---|
| 41 | .PD |
|---|
| 42 | .BI \-\^\-prefix=prefix |
|---|
| 43 | substitute the high bits of the IP addresses with the provided prefix. |
|---|
| 44 | |
|---|
| 45 | .TP |
|---|
| 46 | .PD 0 |
|---|
| 47 | .BI \-c |
|---|
| 48 | .TP |
|---|
| 49 | .PD |
|---|
| 50 | .BI \-\^\-cryptopan=key |
|---|
| 51 | encrypt the IP addresses using the prefix-preserving cryptopan method using |
|---|
| 52 | the key "key". The key can be up to 32 bytes long, and will be padded with |
|---|
| 53 | NUL charactors. |
|---|
| 54 | |
|---|
| 55 | |
|---|
| 56 | .SH EXAMPLES |
|---|
| 57 | .nf |
|---|
| 58 | traceanon \-\^\-cryptopan="fish go moo, oh yes they do" \\ |
|---|
| 59 | \-\^\-encrypt-source \\ |
|---|
| 60 | \-\^\-encrypt-dest \\ |
|---|
| 61 | erf:/traces/unenc.gz \\ |
|---|
| 62 | erf:/traces/enc.gz \\ |
|---|
| 63 | .fi |
|---|
| 64 | |
|---|
| 65 | .SH BUGS |
|---|
| 66 | This software should support encrypting based on the direction/interface flag. |
|---|
| 67 | |
|---|
| 68 | IP addresses inside ARP's are not encrypted. |
|---|
| 69 | |
|---|
| 70 | .SH SEE ALSO |
|---|
| 71 | libtrace(3), tracemerge(1), tracefilter(1), traceconvert(1), tracestats(1), |
|---|
| 72 | tracesummary(1), tracertstats(1), tracesplit(1), tracesplit_dir(1), |
|---|
| 73 | tracereport(1), tracedump(1) |
|---|
| 74 | |
|---|
| 75 | .SH AUTHORS |
|---|
| 76 | Perry Lorier <perry@cs.waikato.ac.nz> |
|---|
