Updated libsodium, updated depdendencies

.gitignore

@@ -1,4 +1,5 @@
 target
 vpncloud-oldnodes
 ._*
+.~*
 deb/vpncloud/vpncloud*

CHANGELOG.md

@@ -16,6 +16,7 @@ This project follows [semantic versioning](http://semver.org).
 - [changed] Passing listen address as &str
 - [changed] Using FNV hash for better performance
 - [changed] Using slice operations instead of loops
+- [changed] Updated libsodium to  1.0.10
 - [fixed] Fixed wrong hex address formatting
 - [fixed] Fixed peer exchange for more than 65000 peers
 - [fixed] Initializing crypto for benchmarks

Cargo.toml

@@ -15,11 +15,11 @@ time = "0.1"
 docopt = "0.6"
 rustc-serialize = "0.3"
 log = "0.3"
-epoll = "0.2"
+epoll = "0.3"
 signal = "0.1"
 nix = "0.5"
 libc = "0.2"
-aligned_alloc = "0.1.1"
+aligned_alloc = "0.1"
 rand = "0.3"
 fnv = "1"
 

README.md

@@ -6,7 +6,8 @@ VpnCloud - Peer-to-Peer VPN
 [![Latest Version](https://img.shields.io/crates/v/vpncloud.svg)](https://crates.io/crates/vpncloud)
 
 **VpnCloud** is a simple VPN over UDP. It creates a virtual network interface on
-the host and forwards all received data via UDP to the destination. It can work
+the host and forwards all received data via UDP to the destination. VpnCloud
+establishes a fully-meshed VPN network in a peer-to-peer manner. It can work
 on TUN devices (IP based) and TAP devices (Ethernet based). Tunneling traffic
 between two nodes can be as easy as:
 
@@ -18,16 +19,15 @@ More details can be found in [the manpage](vpncloud.md).
 Some performance measurements can be found [here](performance.md).
 
 
-### Current Status
+### Project Status
 
-This project is still [under development](CHANGELOG.md) and has yet to reach a stable state.
-However, the main functionality should work and you are invited to test it.
-This is what works:
+This project is still [under development](CHANGELOG.md) but has reached a
+somewhat stable state. VpnCloud features the following functionality:
 
 * Setting up tunnels between two networks via Ethernet (TAP) and IP (TUN)
 * Connecting multiple networks with multiple forwarding behaviors (Hub, Switch, Router)
 * Encrypted connections using [libsodium](https://github.com/jedisct1/libsodium)
-* Automatic peer-to-peer meshing
+* Automatic peer-to-peer meshing, no central servers
 * NAT and (limited) firewall traversal using hole punching
 * Automatic reconnecting when connections are lost
 * Non-native forwarding modes, e.g. IP based learning switch and prefix routed Ethernet networks.
@@ -36,12 +36,14 @@ This is what works:
 
 However there are some open issues:
 
-* Encryption has not been thoroughly reviewed, use with care.
-* The software is not very well tested and the protocol can change.
+* Encryption has not been formally reviewed, use with care.
+* The tests might be missing some corner cases and more field tests would be nice.
 
 Please feel free to help and contribute code.
 
 
 ### Semantic Versioning
 
-This project uses [semantic versioning](http://semver.org). Currently that means that everything can change between versions before 1.0 is finally released.
+This project uses [semantic versioning](http://semver.org). Currently that means
+that everything can change between versions before 1.0 is finally released.
+However I am considering to release 1.0 soon.