1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
|
0.9.0pre1:
* PEERINFO: [CG]
- trust: need *fast* way to check/update trust in peers
(async peerinfo would not be right; certainly not with the current API)
* TRANSPORT: [CG]
- need to implement and test new blacklisting code (server-side only, client API exists)
* TOPOLOGY: [CG]
- needs more testing (especially F2F topology) -- need transport blacklisting to be implemented first!
* FS: [CG]
- support recursive download even if filename is NULL and we hence
do not generate files on disk (use temp_filename)
- bound parallelism (# fs downloads)
- distinguish in performance tracking and event signalling between
downloads that are actually running and those that are merely in the queue
- persistence support (publish, unindex, search, download)
- active migration support (in fs or in datastore or new daemon?)
- gnunet-service-fs (hot-path routing, load-based routing, nitpicks)
- [gnunet-service-fs.c:208]: member 'LocalGetContext::results_bf_size' is never used
- [gnunet-service-fs.c:501]: member 'PendingRequest::used_pids_size' is never used
- [gnunet-service-fs.c:654]: member 'ConnectedPeer::last_client_replies' is never used
- [gnunet-service-fs.c:669]: member 'ConnectedPeer::avg_delay' is never used
- [gnunet-service-fs.c:675]: member 'ConnectedPeer::avg_priority' is never used
- [gnunet-service-fs.c:688]: member 'ConnectedPeer::pending_requests' is never used
- [gnunet-service-fs.c:694]: member 'ConnectedPeer::last_p2p_replies_woff' is never used
- [gnunet-service-fs.c:700]: member 'ConnectedPeer::last_client_replies_woff' is never used
- GAP improvements:
+ active reply route caching design & implementation of service; gap extension!
* TBENCH: [MW]
- good to have for transport/DV evaluation!
* DV: [Nate]
- write DV API (need to move declarations from dv_api.c to gnunet_dv_service.h!)
- implement DV service
- implement DV library (looks done)
- implement DV transport plugin
- implement testcases
- implement performance tests
* UTIL:
- only connect() sockets that are ready (select()) [Nils]
[On W32, we need to select after calling socket before doing connect etc.]
* GNUNET-GTK:
- use g_main_context_set_poll_func to integrate GTK with GNUnet Scheduler!? (YUCK!)
- OR: add scheduler API to enable integration with GTK main loop instead of doing our own select
- use g_main_context_pending, g_main_context_query / g_main_context_check / g_main_context_dispatch
and NEVER g_main_loop_run (can this be done? might be the clean way to do this! But how
to integrate this with "gtk_main"? Docu says:
"It's OK to use the GLib main loop directly instead of gtk_main(), though it involves
slightly more typing. See GMainLoop in the GLib documentation."
=> so maybe it "just works"?
* SETUP:
- design & implement new setup tool
0.9.0pre2:
* TRACEKIT: [MW]
- good to have for DV/DHT evaluation!
* DHT: [Nate]
- implement DHT service
- implement testcases
- implement performance tests
* TRANSPORT:
- HTTP backend [MW]
* ARM: [Safey]
- need to get rid of synchronous API for service starts (cause all kinds of problems)
[=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
- better tracking of which config changes actually need to cause process restarts by ARM.
- listen for requests to discover dependencies between services (and avoid
having to explicitly program start requests)
- better crash management (attach debugging support, capture and analyze
debug output, detect random vs. deterministic crashes)
- shutdown sequence?
* FS: [CG]
- datastore reservation (publishing)
- search: availability probes
- location URIs (publish, search, download)
- non-anonymous FS service (needs DHT)
+ DHT integration for search
+ CS-DHT-functions (DHT-put of LOC)
+ P2P-functions (DHT-get)
- collection API & tests
+ gnunet-pseudonym (collection support)
- implement FS performance tests
+ insert
+ download
+ search
+ unindex
0.9.0pre3:
* Determine RC bugs and fix those!
* TESTING: [Nate]
- modify configuration to allow controlling connections for non-local starts
- testbed creation with topology (needs working F2F topology)
- testbed with churn
- implement testcases for distributed testing
- test basic peer re-configure
- test topology creation
- test churn generation
- consider changing API for peer-group termination to
call continuation when done
* NAT/UPNP: [MW]
- finalize API design
- code clean up
- testing
- integration with transport service
* MYSQL database backends: [CG]
- datacache
- datastore
0.9.0:
* new webpage:
- expand bibliography
- convert documentation pages to books
- update books (especially for developers)
- create good Drupal theme for GNUnet
- make a NICE download page and figure out how to
enable developers to publish TGZs nicely
- port "contact" page
- add content type for "todo" items?
* POSTGRES database backends: [CG]
- datacache
- datastore
* Determine RC bugs and fix those!
0.9.x:
* TRANSPORT: [MW]
- SMTP transport backend
- HTTPS transport backend
+ improved HTTPS support in MHD
+ actual plugin
- Implement method of learning our external addresses from
other peers; need some kind of threshold-based
scheme, limiting both the total number of addresses that we accept
this way as well as requiring multiple confirmations; also, we
should possibly try to confirm that the given address works for
us ourselves (loopback-style) before adding it to the list
+ we may be able to simplify WELCOME messages (no need to add
addresses there anymore, but may help to learn them there anyway...).
+ we probably want some kind of voting/counting for learning IP addresses
(maybe including IP addresses in ads proportional to how often others
report them? we at least need some protection against >64k HELLOs!),
+ provide a way to give the user a list of "learned" IP addresses and
a way to easily "veto" addresses off the list!
=> If MiM attacker uses vetoed address, blacklist the specific IP for
the presumed neighbour!
- implement gnunet-transport (transport configurator / tester)
- UPnP-based IP detection
(Note: build library always, build service when libxml2/etc. are available)
* FS: [CG]
- Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
- Allow checking of presence of search results and/or content via command-line tools
(add options to gnunet-search / gnunet-download to limit search to local peer)
* PEERINFO: [CG]
- expire 'ancient' HELLOs (those without valid addresses AND that
we have not 'used' (for their public keys) in a while; need a way
to track actual 'use')
- make sue we also trigger notifications whenever HELLOs expire
* VPN
Optimizations:
* TCP:
- should use hash map to look up sessions
* STATISTICS:
- should use BIO instead of mmap
* TRANSPORT:
- need to periodically probe latency/transport cost changes & possibly switch transport
- instantly filter addresses from *other* peers that
are *equal* to our own address + port (i.e., localhost:2086). We
no longer filter those for outgoing (helps with loopback testing
and keeps the code clean), but we should filter strictly *impossible*
incoming addresses! This is for efficiency, not correctness.
- should use hash map to look up Neighbours
* HOSTLIST:
- 'server' uses 'GNUNET_PEERINFO_iterate', should probably switch to notification API
(for more instant / up-to-date hostlists at lower cost)
* DATASTORE (?):
- check for duplicates on insertion (currently, same content is frequently
stored again [seen with KBLOCKS and SBLOCKS]!)
Minor features:
* TCP:
- repeatedly resolve hostname and look up interfaces to determine our own IP
- [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
* TRANSPORT:
- [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
* DATACACHE:
- add stats (# bytes available, # bytes used, # PUTs, # GETs, # GETs satisfied)
* FS:
- support inline data in directories for recursive file downloads (fs_download)
|
