An error occurred fetching the project authors.
- 01 Jun, 2021 1 commit
-
-
Joanne Hugé authored
-
- 04 May, 2021 1 commit
-
-
Joanne Hugé authored
If a node restarts and has its address with its country in the cache, it won't set the _country attribute, and will therefore ignore countries when making tunnels. See merge request nexedi/re6stnet!31
-
- 08 Apr, 2021 1 commit
-
-
Julien Muchembled authored
-
- 27 Mar, 2021 1 commit
-
-
Julien Muchembled authored
-
- 23 Mar, 2021 1 commit
-
-
Joanne Hugé authored
Addresses passed to _updateCountry can contain countries if cache.my_address is used to initialize address in BaseTunnelManager init function, which causes resolve to be called with too many arguments.
-
- 22 Mar, 2021 1 commit
-
-
Joanne Hugé authored
In some circumstances, the hello_protocol attribute could get modified on the wrong peer, which would raise an AttributeError. On reception of seqno 1 from a peer with protocol < 7, protocol could be equal to zero which would cause handleHello to not return True, causing the handshake to fail.
-
- 11 Feb, 2021 2 commits
-
-
Joanne Hugé authored
This commit concerns networks that use the --same-country option. We recently discovered that the IP geolocation database contains incorrect entries. To work around this, the protocol needs to be changed by adding the country as 4th field in addresses (the first 3 are: ip, port, protocol) and the new --country option allows a node to announce a country that differs from the one the GeoIP DB. Thanks to the previous commits it's possible to implement backward compatibility, by not sending the 4th field (country) to nodes that can't parse it. Of course, these old nodes would continue to not create appropriate tunnels and after a while, the administrator of the network may decide to increase registry's --min-protocol (7). In a network with only nodes that implement this last version of the protocol, the nodes may only use the GeoIP DB to resolve their own IPs. See merge request !27
-
Julien Muchembled authored
There is a need to be able to extend the protocol without breaking compatibility with old nodes. This is done by sending version.protocol during inter-node handshake, in seqno 1 and seqno 2, so that a node knows what version the peers speak and use appropriate format. This is implemented with partial backward compatibility: handshake with an old node succeeds when the new node does not have to send seqno 1.
-
- 27 Dec, 2019 1 commit
-
-
Julien Muchembled authored
Commit 40d4e496 is not reverted because Python 3 will also require to keep the distinction between blob and text.
-
- 08 Nov, 2019 1 commit
-
-
Julien Muchembled authored
This should fix strange bugs after running the demo for a long time, with certificate renewal happening every few minutes.
-
- 19 Jun, 2019 1 commit
-
-
Killian Lufau authored
HMAC is added in babel call to prevent babel communication between nodes of different re6st networks. This solves the problem of machines in different re6st networks but on the same LAN that exchange routes through babel. The key used to authenticate packets is randomly created on 16 bytes by the registry and sent to nodes when they fetch network parameters. This uses the WIP hmac branch of jech/babeld with Nexedi patches and the added possibility to not check HMAC in incoming packets for better HMAC integration on a HMAC-less network. /reviewed-on !18
-
- 10 Apr, 2019 1 commit
-
-
Killian Lufau authored
The main goal of this is to check if we should keep supporting older distributions. /reviewed-on nexedi/re6stnet!9
-
- 21 Feb, 2019 1 commit
-
-
Killian Lufau authored
/reviewed-on nexedi/re6stnet!7
-
- 25 Sep, 2018 1 commit
-
-
Julien Muchembled authored
-
- 01 Aug, 2018 1 commit
-
-
Julien Muchembled authored
-
- 03 Jul, 2018 1 commit
-
-
Julien Muchembled authored
-
- 02 Jul, 2018 1 commit
-
-
Julien Muchembled authored
-
- 20 Jul, 2017 1 commit
-
-
Julien Muchembled authored
-
- 19 Sep, 2016 1 commit
-
-
Julien Muchembled authored
-
- 31 Aug, 2016 1 commit
-
-
Julien Muchembled authored
-
- 12 Aug, 2016 1 commit
-
-
Julien Muchembled authored
-
- 21 Jun, 2016 1 commit
-
-
Julien Muchembled authored
-
- 13 Jan, 2016 1 commit
-
-
Julien Muchembled authored
-
- 10 Apr, 2015 1 commit
-
-
Julien Muchembled authored
-
- 08 Apr, 2015 1 commit
-
-
Julien Muchembled authored
There is no plan for a default ipv4 route.
-
- 07 Mar, 2015 1 commit
-
-
Julien Muchembled authored
-
- 06 Mar, 2015 4 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Julien Muchembled authored
db.py -> cache.py PeerDB -> Cache peers.db -> cache.db
-
Julien Muchembled authored
-
- 25 Feb, 2015 1 commit
-
-
Julien Muchembled authored
-
- 24 Feb, 2015 2 commits
-
-
Julien Muchembled authored
These modes are partly unified with the normal one by splitting TunnelManager.
-
Julien Muchembled authored
-
- 02 Feb, 2015 1 commit
-
-
Julien Muchembled authored
If too many nodes create client tunnels without serving any, working servers saturate and the network collapses.
-
- 30 Dec, 2014 3 commits
-
-
Julien Muchembled authored
ENETUNREACH is the only error I've ever seen since the beginning of the project.
-
Julien Muchembled authored
The main reason is to speed up recovery from temporary network cut: - by not wasting time trying remaining distant peers that were collected during the last read of the routing table. - by not blacklisting good peers, which would happen if too many of them were retried before network is back
-
Julien Muchembled authored
-
- 26 Dec, 2014 3 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
For consistency with other log messages.
-
Julien Muchembled authored
-