3 - trust: need *fast* way to check/update trust in peers
4 (async peerinfo would not be right; certainly not with the current API)
6 - only connect() sockets that are ready (select()) [Nils]
7 [On W32, we need to select after calling socket before doing connect etc.]
9 - needs more testing (especially F2F topology)
10 - needs to re-try connecting after disconnect (currently, it
11 initially triggers a connection request, but if that connection
12 fails / goes down, it does not retry in a timely fashion;
13 cause seems to be the 'blacklist_after_attempt' being set to 1h,
14 which is rather long -- and should probably be adjusted based on
15 the number of connections / known peers)
16 - If the topology daemon crashes, peers that were put on the
17 blacklist with transport will never be removed from it (until
18 transport service dies); we should use the blacklist notification
19 API to learn about the exact set of blacklisted peers at all times
20 (FIXME: the transport_api implementation of blacklisting
21 also does not work nicely for this since it won't let us know about
22 disconnect-reconnect events and the implicit whitelisting
23 that might happen here; that's not so bad since we will
24 re-blacklist on pre-connect attempts anyway, so this is
25 a minor issue; OTOH, we might want to be more explicit about
26 allowing/forbidding connects on pre-connect to avoid
27 entering connect attempts to just be blacklisted shortly afterwards).
28 - the code uses the term 'blacklist' for both peers that are forbidden
29 to connect (i.e. F2F mode) as well as peers that we currently
30 won't try to actively connect to ourselves (since we just tried);
31 This is confusing. We need two distinct terms (greylist?).
32 - move code to use hash table instead of linked list
33 - instead of periodically discarding blacklisted entries,
34 simply add task that is triggered at the right time (earlier free,
36 - check if new HELLO learned is different from old HELLO
37 before resetting entire state!
39 - API lacks cancellation methods (needed? or is disconnect enough?)
40 - may also want to integrate request queuing here instead of gnunet-service-fs_drq.c
42 - support recursive download even if filename is NULL and we hence
43 do not generate files on disk (use temp_filename)
44 - bound parallelism (# fs downloads)
45 - distinguish in performance tracking and event signalling between
46 downloads that are actually running and those that are merely in the queue
47 - persistence support (publish, unindex, search, download)
48 - active migration support (in fs or in datastore or new daemon?)
49 - gnunet-service-fs (hot-path routing, load-based routing, nitpicks)
50 - [gnunet-service-fs.c:208]: member 'LocalGetContext::results_bf_size' is never used
51 - [gnunet-service-fs.c:501]: member 'PendingRequest::used_pids_size' is never used
52 - [gnunet-service-fs.c:654]: member 'ConnectedPeer::last_client_replies' is never used
53 - [gnunet-service-fs.c:669]: member 'ConnectedPeer::avg_delay' is never used
54 - [gnunet-service-fs.c:675]: member 'ConnectedPeer::avg_priority' is never used
55 - [gnunet-service-fs.c:688]: member 'ConnectedPeer::pending_requests' is never used
56 - [gnunet-service-fs.c:694]: member 'ConnectedPeer::last_p2p_replies_woff' is never used
57 - [gnunet-service-fs.c:700]: member 'ConnectedPeer::last_client_replies_woff' is never used
59 + active reply route caching design & implementation of service; gap extension!
61 - good to have for transport/DV evaluation!
63 - write DV API (need to move declarations from dv_api.c to gnunet_dv_service.h!)
64 - implement DV service
65 - implement DV library (looks done)
66 - implement DV transport plugin
68 - implement performance tests
70 - use g_main_context_set_poll_func to integrate GTK with GNUnet Scheduler!? (YUCK!)
71 - OR: add scheduler API to enable integration with GTK main loop instead of doing our own select
72 - use g_main_context_pending, g_main_context_query / g_main_context_check / g_main_context_dispatch
73 and NEVER g_main_loop_run (can this be done? might be the clean way to do this! But how
74 to integrate this with "gtk_main"? Docu says:
75 "It's OK to use the GLib main loop directly instead of gtk_main(), though it involves
76 slightly more typing. See GMainLoop in the GLib documentation."
77 => so maybe it "just works"?
79 - design & implement new setup tool
83 - good to have for DV/DHT evaluation!
85 - implement DHT service
87 - implement performance tests
91 - need to get rid of synchronous API for service starts (cause all kinds of problems)
92 [=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
93 - better tracking of which config changes actually need to cause process restarts by ARM.
94 - listen for requests to discover dependencies between services (and avoid
95 having to explicitly program start requests)
96 - better crash management (attach debugging support, capture and analyze
97 debug output, detect random vs. deterministic crashes)
100 - datastore reservation (publishing)
101 - search: availability probes
102 - location URIs (publish, search, download)
103 - non-anonymous FS service (needs DHT)
104 + DHT integration for search
105 + CS-DHT-functions (DHT-put of LOC)
106 + P2P-functions (DHT-get)
107 - collection API & tests
108 + gnunet-pseudonym (collection support)
109 - implement FS performance tests
116 * Determine RC bugs and fix those!
118 - modify configuration to allow controlling connections for non-local starts
119 - testbed creation with topology (needs working F2F topology)
121 - implement testcases for distributed testing
122 - test basic peer re-configure
123 - test topology creation
124 - test churn generation
125 - consider changing API for peer-group termination to
126 call continuation when done
128 - finalize API design
131 - integration with transport service
132 * MYSQL database backends: [CG]
138 - expand bibliography
139 - convert documentation pages to books
140 - update books (especially for developers)
141 - create good Drupal theme for GNUnet
142 - make a NICE download page and figure out how to
143 enable developers to publish TGZs nicely
144 - port "contact" page
145 - add content type for "todo" items?
146 * POSTGRES database backends: [CG]
149 * Determine RC bugs and fix those!
153 - SMTP transport backend
154 - HTTPS transport backend
155 + improved HTTPS support in MHD
157 - Implement method of learning our external addresses from
158 other peers; need some kind of threshold-based
159 scheme, limiting both the total number of addresses that we accept
160 this way as well as requiring multiple confirmations; also, we
161 should possibly try to confirm that the given address works for
162 us ourselves (loopback-style) before adding it to the list
163 + we may be able to simplify WELCOME messages (no need to add
164 addresses there anymore, but may help to learn them there anyway...).
165 + we probably want some kind of voting/counting for learning IP addresses
166 (maybe including IP addresses in ads proportional to how often others
167 report them? we at least need some protection against >64k HELLOs!),
168 + provide a way to give the user a list of "learned" IP addresses and
169 a way to easily "veto" addresses off the list!
170 => If MiM attacker uses vetoed address, blacklist the specific IP for
171 the presumed neighbour!
172 - implement gnunet-transport (transport configurator / tester)
173 - UPnP-based IP detection
174 (Note: build library always, build service when libxml2/etc. are available)
176 - Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
177 - Allow checking of presence of search results and/or content via command-line tools
178 (add options to gnunet-search / gnunet-download to limit search to local peer)
180 - expire 'ancient' HELLOs (those without valid addresses AND that
181 we have not 'used' (for their public keys) in a while; need a way
182 to track actual 'use')
183 - make sue we also trigger notifications whenever HELLOs expire
190 - should use hash map to look up sessions
192 - api creates many, many short-lived TCP connections; either some
193 clients should use the API differently or we need to change the
194 API to enable re-use of connections to the service
196 - should use BIO instead of mmap
198 - need to periodically probe latency/transport cost changes & possibly switch transport
199 - instantly filter addresses from *other* peers that
200 are *equal* to our own address + port (i.e., localhost:2086). We
201 no longer filter those for outgoing (helps with loopback testing
202 and keeps the code clean), but we should filter strictly *impossible*
203 incoming addresses! This is for efficiency, not correctness.
204 - should use hash map to look up Neighbours
206 - 'server' uses 'GNUNET_PEERINFO_iterate', should probably switch to notification API
207 (for more instant / up-to-date hostlists at lower cost) [OPTIMIZATION]
209 - check for duplicates on insertion (currently, same content is frequently
210 stored again [seen with KBLOCKS and SBLOCKS]!)
214 - repeatedly resolve hostname and look up interfaces to determine our own IP
215 - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
217 - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
219 - add stats (# bytes available, # bytes used, # PUTs, # GETs, # GETs satisfied)
221 - support inline data in directories for recursive file downloads (fs_download)