--- gvpe/NEWS	2003/10/22 00:42:53	1.11
+++ gvpe/NEWS	2004/01/29 19:22:05	1.17
@@ -1,10 +1,31 @@
+POSSIBLE TODO send sha1hash of public key for better error reporting(?)
+POSSIBLE TODO check own keypair for better error reporting
+TODO vpn::tap_ev does not handle EOF well, or does it? (CHECK)
+TODO vpn::tcpv4_ev does not handle EOF well, or does it? (CHECK)
+TODO tcp_connection::tcpv4_ev does not handle EOF well, or does it? (CHECK)
 
-TODO send sha1hash of public key
-TODO check own keypair for correctness
+1.5
+   - protocol version 0.1, compatible with older releases.
+   - vped will refuse to start when hostkey and public key do not match.
+   - updated lzf code to version 1.2.
+   - better error reporting for "unusual" conditions, like failing
+     to allocate memory, that should not normally happen and
+     will otherwise result in spurious other error messages. Also
+     adds paranoid checks in case openssl's API changes in a bad way.
+   - fix a bug where queued vpn packets were cleared to zero. while
+     this doesn't affect security, it did cause warning messages and
+     unnecessary connectivity delays.
+
+1.4 Sat Jan 17 15:49:21 CET 2004
+   - protocol version 0.1, compatible with older releases.
    - better retry behaviour on key mismatch.
+   - use select-based io_manager instead of poll-based one.
+   - share io manager between rxvt-unicode and vpe.
+   - sooo many *BSD workarounds because no BSD I could find is even
+     remotely POSIX-compatible.
 
 1.2 Fri Oct 17 03:44:44 CEST 2003
-   - protocol version 0.1
+   - protocol version 0.1.
    - tincd kernel interface code imported, more supported platforms
      (native/linux (2.4), tincd/linux (2.2 and 2.4), tincd/freebsd,
      native/cygwin).
@@ -19,9 +40,9 @@
    - added doc/complex-example to the distribution.
 
 1.0
-   - protocol version 0.1
+   - protocol version 0.1.
    - tweaked various timeouts to help very slow (486) class
      machines or nets with many hosts.
    - tweaked rate-limiting to be more forgiving for hosts
-     connecting through routers (not a fix)
+     connecting through routers (not a fix).