Added documentation website content, and a workflow to publish it to GitHub Pages
* Copied, rearranged and modified the contents of the old site directory for Jekyll static site generator, into the website directory * Added some Jekyll-specific things for looks, including: * _config.yaml, Gemfile.* and 404.html files * _data, _layouts and assets directories and their content * Added .github/workflows/github-pages-publish.yml workflow
This commit is contained in:
1 parent
92779f3e57
commit
e2db8a25bd
82 files changed
+6162
No files matched your search
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Encryption and Weave Net
|
||||
menu_order: 50
|
||||
search_type: Documentation
|
||||
---
|
||||
|
||||
|
||||
Weave Net peers
|
||||
[communicate with each other over both TCP and UDP]({{ '/concepts/how-it-works' | relative_url }}). This
|
||||
communication
|
||||
[can be encrypted]({{ '/tasks/manage/security-untrusted-networks' | relative_url }}).
|
||||
|
||||
Encryption of control plane traffic (TCP) and data plane traffic (UDP) of sleeve
|
||||
overlay is accomplished using the [NaCl](http://nacl.cr.yp.to/)
|
||||
crypto libraries, employing Curve25519, XSalsa20 and Poly1305 to
|
||||
encrypt and authenticate messages. Weave Net protects against
|
||||
injection and replay attacks for traffic forwarded between peers.
|
||||
|
||||
NaCl was selected because of its good reputation both in terms of
|
||||
selection and implementation of ciphers, but equally importantly, its
|
||||
clear APIs, good documentation and high-quality
|
||||
[go implementation](https://godoc.org/golang.org/x/crypto/nacl). It is
|
||||
quite difficult to use NaCl incorrectly. Contrast this with libraries
|
||||
such as OpenSSL where the library and its APIs are vast in size,
|
||||
poorly documented, and easily used wrongly.
|
||||
|
||||
There are some similarities between Weave Net's crypto and
|
||||
[TLS](https://tools.ietf.org/html/rfc4346). Weave Net does not need to cater
|
||||
for multiple cipher suites, certificate exchange and other
|
||||
requirements emanating from X509, and a number of other features. This
|
||||
simplifies the protocol and implementation considerably. On the other
|
||||
hand, Weave Net needs to support UDP transports, and while there are
|
||||
extensions to TLS such as [DTLS](https://tools.ietf.org/html/rfc4347)
|
||||
which can operate over UDP, these are not widely implemented and
|
||||
deployed.
|
||||
|
||||
In the case of fast datapath, data plane traffic is encrypted by using
|
||||
[ESP of IPsec](https://tools.ietf.org/html/rfc2406).
|
||||
The process of encryption is handled by the Linux kernel and is controlled via
|
||||
the IP transformation framework (XFRM).
|
||||
|
||||
**See Also**
|
||||
|
||||
* [How Weave Implements Encryption]({{ '/concepts/encryption-implementation' | relative_url }})
|
||||
* [Securing Containers Across Untrusted Networks]({{ '/tasks/manage/security-untrusted-networks' | relative_url }})
|
||||
Reference in new issue
Block a user