| 1 | GVPE NEWS |
1 | GVPE NEWS |
| 2 | |
2 | |
|
|
3 | TODO: bridge mode, finally? |
|
|
4 | TODO: gcm mode? |
|
|
5 | TODO: replace ripemd160 as the only authentication hash. |
|
|
6 | TODO: increase rsa size. |
|
|
7 | TODO: replace transport bits by transport endpoint structs? |
|
|
8 | TODO: ecdh to avoid session replay attacks |
|
|
9 | TODO: http://incog-izick.blogspot.de/2011/08/using-openssl-aes-gcm.html |
|
|
10 | TODO: http://stackoverflow.com/questions/12153009/openssl-c-example-of-aes-gcm-using-evp-interfaces |
|
|
11 | |
|
|
12 | proposed: 3 types, req, resreq, res |
|
|
13 | |
|
|
14 | req (hmac1) rsa(seqno1 hmac1 aes1 seqno2 hmac2 aes2 auth) ecdh1 |
|
|
15 | res (hmac1) hash(rsa-contents) ecdh2 |
|
|
16 | |
|
|
17 | req hmac0(*) rsa(seqno hmac0 hmac aes auth) hkdf-salt ecdh1 |
|
|
18 | res hmac0(rsa-contents ecdh2) |
|
|
19 | hmac_key = hkdf(hkdf-salt, hmac | ecdh) |
|
|
20 | aes_key = hkdf(hkdf-salt, aes | ecdh) |
|
|
21 | |
|
|
22 | - INCOMPATIBLE CHANGE: core protocol version 1.0. |
|
|
23 | - while individual packets couldn't be replayed, a whole session |
|
|
24 | could be replayed - this has been fixed by an extra key exchange. |
|
|
25 | - in addition to rsa key exchange and authentication, the handshake now |
|
|
26 | adds a diffie-hellman key exchange (using curve25119) for perfect |
|
|
27 | forward secrecy. mac and cipher keys are derived using HKDF. |
|
|
28 | - rsa key sizes are now configurable and larger (default is 3072). |
|
|
29 | correspondingly, the minimum mtu is no longer 296 but 576. |
|
|
30 | - fixed a potential (unverified) buffer overrun on rsa decryption. |
|
|
31 | - RAND_bytes was used when generating session keys, potentially |
|
|
32 | leading to temporary freezes when entropy was low. |
|
|
33 | - gvpectrl no longer generates all missing public keys, but |
|
|
34 | only missing private keys. private keys are also put |
|
|
35 | into the configured location. |
|
|
36 | - the pid-file now accepts %s as nodename as elsewhere. |
|
|
37 | |
|
|
38 | 2.25 Sat Jul 13 06:42:33 CEST 2013 |
| 3 | - INCOMPATIBLE CHANGE: no longer enable udp protocol if no other |
39 | - INCOMPATIBLE CHANGE: no longer enable udp protocol if no other |
| 4 | protocols are enabled - this is necessary when you have nodes with |
40 | protocols are enabled - this is necessary when you have nodes with |
| 5 | completely unknown protocols, to force mediated connection requests. |
41 | completely unknown protocols, to force mediated connection requests. |
| 6 | - INCOMPATIBLE CHANGE: dns transport protocol bumped to version 2. |
42 | - INCOMPATIBLE CHANGE: dns transport protocol bumped to version 2. |
|
|
43 | - core protocol version 0.1, compatible with older releases. |
|
|
44 | - switch to using RSA_generate_key_ex, which is the badly documented |
|
|
45 | and needlessly more complicated replacement for the RSA_generate_key |
|
|
46 | function which is now deprecated. |
|
|
47 | - support additional hmac hashes: sha256 and sha512, usually truncated. |
|
|
48 | - change public exponent for rsa keys from 65535 to 65537, for |
|
|
49 | efficiency reasons - only affects new keys. |
|
|
50 | - nodes would sometimes declare transport endpoints valid despite |
|
|
51 | the protocol not being configured locally. |
|
|
52 | - new global configuration options: chroot, chuser, chuid, chgid, |
|
|
53 | to chroot to a specified or anonymous new root, and change user id. |
|
|
54 | - new global configuration options seed_device and seed_interval, |
|
|
55 | to configure another device than /dev/urandom for random seeds, |
|
|
56 | and to configure a regular imterval to reseed the rng. |
|
|
57 | - prefer inet_aton over gethostbyname, as the latter is not guaranteed |
|
|
58 | to "resolve" literal ip addresses. |
| 7 | - configure didn't detect openssl 1.0 because SHA1_version became private |
59 | - configure didn't detect openssl 1.0 because SHA1_version became private |
| 8 | (patch by TANIGUCHI Takaki). |
60 | (patch by TANIGUCHI Takaki). |
| 9 | - core protocol version 0.1, compatible with older releases. |
|
|
| 10 | - fix a bug where nodes would tell the other side that it supports |
61 | - fix a bug where nodes would tell the other side that it supports |
| 11 | the same protocols as that other side, instead of its own. |
62 | the same protocols as that other side, instead of its own. |
| 12 | - add zlib when found, as openssl depends on it in newer versions. |
63 | - add zlib when found, as openssl depends on it in newer versions. |
| 13 | - work around append-bugs in uclibc by using an extra seek. |
64 | - work around append-bugs in uclibc by using an extra seek. |
| 14 | - new "include" directive for the config file. |
65 | - new "include" directive for the config file. |
| … | |
… | |
| 24 | - back off far quicker in dns tunnel when idling - increases |
75 | - back off far quicker in dns tunnel when idling - increases |
| 25 | latency on an idle link somewhat, but avoids hundreds of |
76 | latency on an idle link somewhat, but avoids hundreds of |
| 26 | needless packets. |
77 | needless packets. |
| 27 | - poll more aggressively when idling in dns (poll once per |
78 | - poll more aggressively when idling in dns (poll once per |
| 28 | second as opposed to once per 5 seconds). |
79 | second as opposed to once per 5 seconds). |
|
|
80 | - reduce dns send payload size to allow greater rate of ack |
|
|
81 | messages (should help sack and ipv6). |
|
|
82 | - allow for ip options in rawip/icmp transports, even though gvpe |
|
|
83 | doesn't generate them. |
|
|
84 | - upgrade to autoconf 2.69, automake 1.11. |
| 29 | - upgrade to libev 4 API. |
85 | - upgrade to libev 4 API. |
|
|
86 | - replace COPYING file by actual GPLv3 - files were relicensed to GPLv3 |
|
|
87 | earlier but COPYING was forgotten. |
| 30 | |
88 | |
| 31 | 2.24 Sat Feb 12 05:15:48 CET 2011 |
89 | 2.24 Sat Feb 12 05:15:48 CET 2011 |
| 32 | - protocol version 0.1, compatible with older releases. |
90 | - protocol version 0.1, compatible with older releases. |
| 33 | - due to a bug, when packets were lost, a connection could go into a |
91 | - due to a bug, when packets were lost, a connection could go into a |
| 34 | state where a ping/connection request from another node would be |
92 | state where a ping/connection request from another node would be |
