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