1 | GVPE NEWS |
1 | GVPE NEWS |
|
|
2 | |
|
|
3 | TODO: bridge mode, finally? |
|
|
4 | TODO: gcm mode? |
|
|
5 | TODO: replace ripemd160 as the only authentication hash. |
|
|
6 | TODO: increase rsa size. |
2 | |
7 | |
3 | - INCOMPATIBLE CHANGE: no longer enable udp protocol if no other |
8 | - INCOMPATIBLE CHANGE: no longer enable udp protocol if no other |
4 | protocols are enabled - this is necessary when you have nodes with |
9 | protocols are enabled - this is necessary when you have nodes with |
5 | completely unknown protocols, to force mediated connection requests. |
10 | completely unknown protocols, to force mediated connection requests. |
|
|
11 | - INCOMPATIBLE CHANGE: dns transport protocol bumped to version 2. |
|
|
12 | - core protocol version 0.1, compatible with older releases. |
|
|
13 | - switch to using RSA_generate_key_ex, which is the badly documented |
|
|
14 | and needlessly more complicated replacement for the RSA_generate_key |
|
|
15 | function which is now deprecated. |
|
|
16 | - support additional hmac hashes: sha256 and sha512, usually truncated. |
|
|
17 | - change public exponent for rsa keys from 65535 to 65537, for |
|
|
18 | efficiency reasons - only affects new keys. |
|
|
19 | - nodes would sometimes declare transport endpoints valid despite |
|
|
20 | the protocol not being configured locally. |
|
|
21 | - new global configuration options: chroot, chuser, chuid, chgid, |
|
|
22 | to chroot to a specified or anonymous new root, and change user id. |
|
|
23 | - new global configuration options seed_device and seed_interval, |
|
|
24 | to configure another device than /dev/urandom for random seeds, |
|
|
25 | and to configure a regular imterval to reseed the rng. |
|
|
26 | - prefer inet_aton over gethostbyname, as the latter is not guaranteed |
|
|
27 | to "resolve" literal ip addresses. |
|
|
28 | - configure didn't detect openssl 1.0 because SHA1_version became private |
|
|
29 | (patch by TANIGUCHI Takaki). |
6 | - fix a bug where nodes would tell the other side that it supports |
30 | - fix a bug where nodes would tell the other side that it supports |
7 | the same protocols as that other side, instead of its own. |
31 | the same protocols as that other side, instead of its own. |
|
|
32 | - add zlib when found, as openssl depends on it in newer versions. |
|
|
33 | - work around append-bugs in uclibc by using an extra seek. |
|
|
34 | - new "include" directive for the config file. |
|
|
35 | - gvpectrl no longer evaluates any "on" directives. |
|
|
36 | - icmp and rawip protocols weren't upgradable to each other. |
|
|
37 | - major, but incremental, dns transport improvements: |
|
|
38 | - do not simply abort in some error cases in the dns transport, |
|
|
39 | but try to recover. |
|
|
40 | - allow lowercase/uppercase alises for base-n encodings that do |
|
|
41 | not rely on case. |
|
|
42 | - use base26 instead of base22 encoding for dns syn's, and |
|
|
43 | base36 instead of base22 for headers (saves one byte/packet). |
|
|
44 | - back off far quicker in dns tunnel when idling - increases |
|
|
45 | latency on an idle link somewhat, but avoids hundreds of |
|
|
46 | needless packets. |
|
|
47 | - poll more aggressively when idling in dns (poll once per |
|
|
48 | second as opposed to once per 5 seconds). |
|
|
49 | - reduce dns send payload size to allow greater rate of ack |
|
|
50 | messages (should help sack and ipv6). |
|
|
51 | - allow for ip options in rawip/icmp transports, even though gvpe |
|
|
52 | doesn't generate them. |
|
|
53 | - upgrade to autoconf 2.69, automake 1.11. |
|
|
54 | - upgrade to libev 4 API. |
|
|
55 | - replace COPYING file by actual GPLv3 - files were relicensed to GPLv3 |
|
|
56 | earlier but COPYING was forgotten. |
8 | |
57 | |
9 | 2.24 Sat Feb 12 05:15:48 CET 2011 |
58 | 2.24 Sat Feb 12 05:15:48 CET 2011 |
10 | - protocol version 0.1, compatible with older releases. |
59 | - protocol version 0.1, compatible with older releases. |
11 | - due to a bug, when packets were lost, a connection could go into a |
60 | - due to a bug, when packets were lost, a connection could go into a |
12 | state where a ping/connection request from another node would be |
61 | state where a ping/connection request from another node would be |