1 This file lists minor work items (also possibly called "known bugs").
2 We are not tracking them in Mantis yet since there are too many and no
3 sane end-user should care about this codebase yet anyway.
7 - container_bloomfilter: improve efficiency (see FIXME)
8 - only connect() sockets that are ready (select()) [Nils]
9 [On W32, we need to select after calling socket before
12 - transport_api: support forcing disconnects through low quotas!
13 (required for working F2F support!)
14 - API: consider having core provide deadline information for each message
15 (likely important for DV plugin which wants to loop back!)
16 - implement transport API to pretty-print transport address
17 + transport_api extension (API extension!)
18 + service-transport extension (protocol extension)
19 - add calls to statistics in various places
20 - implement gnunet-transport (transport configurator / tester)
21 - UPnP-based IP detection
22 (Note: build library always, build service when libxml2/etc. are available)
23 - instantly filter addresses from *other* peers that
24 are *equal* to our own address + port (i.e., localhost:2086). We
25 no longer filter those for outgoing (helps with loopback testing
26 and keeps the code clean), but we should filter strictly *impossible*
27 incoming addresses! This is for efficiency, not correctness.
28 - We currently are happy to take any address told to us in a WELCOME
29 to our set of addresses; we should have some minimal threshold-based
30 scheme, limiting both the total number of addresses that we accept
31 this way as well as requiring multiple confirmations; also, we
32 should possibly try to confirm that the given address works for
33 us ourselves (loopback-style) before adding it to the list
35 + we may be able to simplify WELCOME messages (no need to add
36 addresses there anymore, but may help to learn them there anyway...).
37 + we probably want some kind of voting/counting for learning IP addresses
38 (maybe including IP addresses in ads proportional to how often others
39 report them? we at least need some protection against >64k HELLOs!),
40 + provide a way to give the user a list of "learned" IP addresses and
41 a way to easily "veto" addresses off the list!
42 => If MiM attacker uses vetoed address, blacklist the specific IP for
43 the presumed neighbour!
44 - not sure current way of doing ACKs works well-enough
45 with unreliable transports where the ACK maybe lost;
46 the "is_new" check would then possibly prevent future
47 ACKs to be delivered, all while we're happily
48 receiving messages from that peer! Worse, the other
49 peer won't generate another ACK since it thinks we're
50 connected just fine...
52 + How necessary is ACKing in the first place? (alternatives?)
53 + Should we transmit ACKs in response to every HELLO? (would that
54 fully address the problem?)
55 - latency measurements implemented in the transport
56 plugins makes it only work for bi-di transports
57 and results in code replication
58 - should latency be included in the ReceiveCallback and
59 NotifyConnect or passed on request?
60 - FIXME's with latency being simply set to 0 in a few places
61 - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used
62 - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used
65 - [./fs/gnunet-service-fs.c:208]: (style) struct or union member 'LocalGetContext::results_bf_size' is never used
66 - [./fs/gnunet-service-fs.c:501]: (style) struct or union member 'PendingRequest::used_pids_size' is never used
67 - [./fs/gnunet-service-fs.c:654]: (style) struct or union member 'ConnectedPeer::last_client_replies' is never used
68 - [./fs/gnunet-service-fs.c:669]: (style) struct or union member 'ConnectedPeer::avg_delay' is never used
69 - [./fs/gnunet-service-fs.c:675]: (style) struct or union member 'ConnectedPeer::avg_priority' is never used
70 - [./fs/gnunet-service-fs.c:688]: (style) struct or union member 'ConnectedPeer::pending_requests' is never used
71 - [./fs/gnunet-service-fs.c:694]: (style) struct or union member 'ConnectedPeer::last_p2p_replies_woff' is never used
72 - [./fs/gnunet-service-fs.c:700]: (style) struct or union member 'ConnectedPeer::last_client_replies_woff' is never used
75 - [./topology/gnunet-daemon-topology.c:94]: (style) struct or union member 'PeerList::last_hello_sent' is never used
78 - auto-generate "defaults.conf" using gnunet-setup from "config.scm"
79 - integrate all options into "config.scm"
80 - change config-file writing to exclude options set to default values
82 - implement exponential back-off for service restarts
83 - better tracking of which config changes actually need to cause process restarts by ARM.
84 - have way to specify dependencies between services (to manage ARM restarts better)
86 - code currently notifies clients about "encrypted" connections being up well before
87 we get the encrypted PONG; sometimes this may be OK (for topology killing
88 unwanted connnections), but of course not in general. I suspect we want
89 to signal on PONG and have topology hook directly into transport to
90 kill plaintext connections before they have a chance to become encrypted
91 (may require minor hack in transport API)
92 - [./core/gnunet-service-core.c:469]: (style) struct or union member 'Neighbour::message_queue_size' is never used
93 - [./core/test_core_api_start_only.c:50]: (style) struct or union member 'PeerContext::id' is never used
96 - Better SSL-support for MHD
99 - active reply route caching design & implementation of service,
102 - consider changing API for peer-group termination to
103 call continuation when done