ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/gvpe/NEWS
(Generate patch)

Comparing gvpe/NEWS (file contents):
Revision 1.109 by root, Fri Jul 5 10:05:15 2013 UTC vs.
Revision 1.119 by root, Fri Oct 11 04:07:24 2013 UTC

1GVPE NEWS 1GVPE NEWS
2 2
3TODO: bridge mode, finally? 3TODO: bridge mode, finally?
4TODO: gcm mode?
5TODO: replace ripemd160 as the only authentication hash.
6TODO: increase rsa size.
7TODO: replace transport bits by transport endpoint structs?
8TODO: ecdh to avoid session replay attacks
9TODO: http://incog-izick.blogspot.de/2011/08/using-openssl-aes-gcm.html
10TODO: http://stackoverflow.com/questions/12153009/openssl-c-example-of-aes-gcm-using-evp-interfaces
4 11
12proposed: 3 types, req, resreq, res
13
14req (hmac1) rsa(seqno1 hmac1 aes1 seqno2 hmac2 aes2 auth) ecdh1
15res (hmac1) hash(rsa-contents) ecdh2
16
17req hmac0(*) rsa(seqno hmac0 hmac aes auth) hkdf-salt ecdh1
18res hmac0(rsa-contents ecdh2)
19 hmac_key = hkdf(hkdf-salt, hmac | ecdh)
20 aes_key = hkdf(hkdf-salt, aes | ecdh)
21
22TODO: protocol magic fixen(!!!)
23TODO: "global"
24TODO: verify
25TODO: make sense of overhead calculation
26TODO: if-up &c should not be scripts?
27 - INCOMPATIBLE CHANGE: core protocol version 1.0.
28 - INCOMPATIBLE CHANGE: node sextions are now introduced
29 with "node nodename", not "node = nodename".
30 - while individual packets couldn't be replayed, a whole session
31 could be replayed - this has been fixed by an extra key exchange.
32 - in addition to rsa key exchange and authentication, the handshake now
33 adds a diffie-hellman key exchange (using curve25119) for perfect
34 forward secrecy. mac and cipher keys are derived using HKDF.
35 - rsa key sizes are now configurable and larger (default is 3072).
36 correspondingly, the minimum mtu is no longer 296 but 576.
37 - fixed a potential (unverified) buffer overrun on rsa decryption.
38 - router reconnects could cause excessive rekeying on other connections.
39 - gvpectrl no longer generates all missing public keys, but
40 only missing private keys. private keys are also put
41 into the configured location.
42 - the pid-file now accepts %s as nodename as elsewhere.
43 - no longer use RAND_bytes to generate session keys - you NEED
44 a real source of entropy now (e.g. egd or /dev/random - see the
45 openssl documentation).
46 - multiple node statements for the same node are now supported
47 and will be merged.
48 - a new directive "global" switches back to the global section
49 of the config file.
50 - 12 random prefix bytes are now properly supported, leading to
51 a fully random IV.
52 - use aes with a random key in counter-mode to generate IVs,
53 for speed reasons (generating 12 random bytes with openssl can
54 take longer than encrypting and mac'ing a 1.5kb packet, and IVs
55 do not need to be cryptographically strong random numbers
56 (and in fact, shouldn't be)).
57 - if-up scripts can now be specified with absolute paths.
58 - new global option: serial, to detect configuration mismatches.
59 - use HKDF as authentication proof, not HMAC or a plain hash
60 (hint by Ilmari Karonen).
61 - during rekeying or conenction establishments, hmac authentication
62 errors could occur and reset the connection. Transient hmac
63 authentication errors are now being ignored for 3 seconds.
64 - log the reason for a conneciton loss.
65
662.25 Sat Jul 13 06:42:33 CEST 2013
5 - INCOMPATIBLE CHANGE: no longer enable udp protocol if no other 67 - INCOMPATIBLE CHANGE: no longer enable udp protocol if no other
6 protocols are enabled - this is necessary when you have nodes with 68 protocols are enabled - this is necessary when you have nodes with
7 completely unknown protocols, to force mediated connection requests. 69 completely unknown protocols, to force mediated connection requests.
8 - INCOMPATIBLE CHANGE: dns transport protocol bumped to version 2. 70 - INCOMPATIBLE CHANGE: dns transport protocol bumped to version 2.
71 - core protocol version 0.1, compatible with older releases.
9 - switch to using RSA_generate_key_ex, which is the undocumented 72 - switch to using RSA_generate_key_ex, which is the badly documented
10 and needlessly more complicated replacement for the RSA_generate_key 73 and needlessly more complicated replacement for the RSA_generate_key
11 function which is now deprecated. 74 function which is now deprecated.
75 - support additional hmac hashes: sha256 and sha512, usually truncated.
12 - change public exponent for rsa keys from 65535 to 65537, for 76 - change public exponent for rsa keys from 65535 to 65537, for
13 efficiency reasons. 77 efficiency reasons - only affects new keys.
14 - nodes would sometimes declare transport endpoints valid despite 78 - nodes would sometimes declare transport endpoints valid despite
15 the protocol not being configured locally. 79 the protocol not being configured locally.
16 - core protocol version 0.1, compatible with older releases.
17 - new global configuration options: chroot, chuser, chuid, chgid, 80 - new global configuration options: chroot, chuser, chuid, chgid,
18 to chroot to a specified or anonymous new root, and change user id. 81 to chroot to a specified or anonymous new root, and change user id.
82 - new global configuration options seed_device and seed_interval,
83 to configure another device than /dev/urandom for random seeds,
84 and to configure a regular interval to reseed the rng.
19 - prefer inet_aton over gethostbyname, as the latter is not guaranteed 85 - prefer inet_aton over gethostbyname, as the latter is not guaranteed
20 to "resolve" literal ip addresses. 86 to "resolve" literal ip addresses.
21 - configure didn't detect openssl 1.0 because SHA1_version became private 87 - configure didn't detect openssl 1.0 because SHA1_version became private
22 (patch by TANIGUCHI Takaki). 88 (patch by TANIGUCHI Takaki).
23 - fix a bug where nodes would tell the other side that it supports 89 - fix a bug where nodes would tell the other side that it supports
28 - gvpectrl no longer evaluates any "on" directives. 94 - gvpectrl no longer evaluates any "on" directives.
29 - icmp and rawip protocols weren't upgradable to each other. 95 - icmp and rawip protocols weren't upgradable to each other.
30 - major, but incremental, dns transport improvements: 96 - major, but incremental, dns transport improvements:
31 - do not simply abort in some error cases in the dns transport, 97 - do not simply abort in some error cases in the dns transport,
32 but try to recover. 98 but try to recover.
33 - allow lowercase/uppercase alises for base-n encodings that do 99 - allow lowercase/uppercase aliases for base-n encodings that do
34 not rely on case. 100 not rely on case.
35 - use base26 instead of base22 encoding for dns syn's, and 101 - use base26 instead of base22 encoding for dns syn's, and
36 base36 instead of base22 for headers (saves one byte/packet). 102 base36 instead of base22 for headers (saves one byte/packet).
37 - back off far quicker in dns tunnel when idling - increases 103 - back off far quicker in dns tunnel when idling - increases
38 latency on an idle link somewhat, but avoids hundreds of 104 latency on an idle link somewhat, but avoids hundreds of
41 second as opposed to once per 5 seconds). 107 second as opposed to once per 5 seconds).
42 - reduce dns send payload size to allow greater rate of ack 108 - reduce dns send payload size to allow greater rate of ack
43 messages (should help sack and ipv6). 109 messages (should help sack and ipv6).
44 - allow for ip options in rawip/icmp transports, even though gvpe 110 - allow for ip options in rawip/icmp transports, even though gvpe
45 doesn't generate them. 111 doesn't generate them.
112 - upgrade to autoconf 2.69, automake 1.11.
46 - upgrade to libev 4 API. 113 - upgrade to libev 4 API.
114 - replace COPYING file by actual GPLv3 - files were relicensed to GPLv3
115 earlier but COPYING was forgotten.
47 116
482.24 Sat Feb 12 05:15:48 CET 2011 1172.24 Sat Feb 12 05:15:48 CET 2011
49 - protocol version 0.1, compatible with older releases. 118 - protocol version 0.1, compatible with older releases.
50 - due to a bug, when packets were lost, a connection could go into a 119 - due to a bug, when packets were lost, a connection could go into a
51 state where a ping/connection request from another node would be 120 state where a ping/connection request from another node would be

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines