DeforaNetworks/fwknop
DeforaNetworks/fwknop
3
0
Fork 0
Code Releases Activity

include link to DefCon 14 presentation on fwknop + Tor

Browse Source
This commit is contained in:
Michael Rash 2015-06-14 08:41:06 -04:00
parent 9ce5ad47c0
commit 70fd1c990f
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -132,11 +132,13 @@ The following is a complete list of features supported by the fwknop project:
as the port over which the follow-on connection is made via the iptables NAT as the port over which the follow-on connection is made via the iptables NAT
capabilities. The later applies to forwarded connections to internal services and capabilities. The later applies to forwarded connections to internal services and
to access granted to local sockets on the system running fwknopd. to access granted to local sockets on the system running fwknopd.
* Integration with Tor (see my DefCon 14 presentation). Note that because Tor uses * Integration with Tor (as described in this
TCP for transport, sending SPA packets through the Tor network requires that each [DefCon 14](http://www.cipherdyne.org/fwknop/docs/talks/dc14_fwknop_slides.pdf) presentation).
SPA packet is sent over an established TCP connection, so technically this breaks Note that because Tor uses TCP for transport, sending SPA packets through the Tor
the "single" aspect of "Single Packet Authorization". However, Tor provides network requires that each SPA packet is sent over an established TCP connection,
anonymity benefits that can outweigh this consideration in some deployments. so technically this breaks the "single" aspect of "Single Packet Authorization".
However, Tor provides anonymity benefits that can outweigh this consideration in
some deployments.
* Implements a versioned protocol for SPA communications, so it is easy to extend * Implements a versioned protocol for SPA communications, so it is easy to extend
the protocol to offer new SPA message types and maintain backwards compatibility the protocol to offer new SPA message types and maintain backwards compatibility
with older fwknop clients at the same time. with older fwknop clients at the same time.