initial support for DHT RSS feeds
This commit is contained in:
@@ -1388,6 +1388,7 @@ struct dht_settings
|
||||
int max_peers_reply;
|
||||
int search_branching;
|
||||
int max_fail_count;
|
||||
int max_torrents;
|
||||
bool restrict_routing_ips;
|
||||
bool restrict_search_ips;
|
||||
};
|
||||
@@ -1402,6 +1403,12 @@ before it is removed from the routing table. If there are known working nodes
|
||||
that are ready to replace a failing node, it will be replaced immediately,
|
||||
this limit is only used to clear out nodes that don't have any node that can
|
||||
replace them.</p>
|
||||
<p><tt class="docutils literal"><span class="pre">max_torrents</span></tt> is the total number of torrents to track from the DHT. This
|
||||
is simply an upper limit to make sure malicious DHT nodes cannot make us allocate
|
||||
an unbounded amount of memory.</p>
|
||||
<p><tt class="docutils literal"><span class="pre">max_feed_items</span></tt> is the total number of feed items to store from the DHT. This
|
||||
is simply an upper limit to make sure malicious DHT nodes cannot make us allocate
|
||||
an unbounded amount of memory.</p>
|
||||
<p><tt class="docutils literal"><span class="pre">restrict_routing_ips</span></tt> determines if the routing table entries should restrict
|
||||
entries to one per IP. This defaults to true, which helps mitigate some attacks
|
||||
on the DHT. It prevents adding multiple nodes with IPs with a very close CIDR
|
||||
@@ -4178,7 +4185,6 @@ struct session_settings
|
||||
bool low_prio_disk;
|
||||
int local_service_announce_interval;
|
||||
int dht_announce_interval;
|
||||
int dht_max_torrents;
|
||||
|
||||
int udp_tracker_token_expiry;
|
||||
bool volatile_read_cache;
|
||||
|
Reference in New Issue
Block a user