0.9.0pre3: [2'11] * NAT/UPNP: [Milan / MW] - [#1609] code clean up - testing - integration with transport service: + test TCP + implement UDP, HTTP/HTTPS * Transport: - ATS crashes [MW] - UDP fragmentation [MW] * CORE: - Core API's peer_change_preference leaks 'irc' and Core API's notify_transmit_ready leaks 'th'! * FS [CG] - test*.py fail - download of 100 MB file from 'leach' peer hung due to failure of core-api to call back after a change preference request (structs indicate request was transmitted but reply never received?) => try again! - test_gnunet_service_fs_p2p: => sometimes DATASTORE get operation fails to queue on target (why?) => do we need to just make the queue larger? - with core queue size of 1, we get notify_transmit_ready from core API returning NULL (why? ok? just have larger queue?) - other runs (-L DEBUG) with downloads using the new 'trust' test show non-deterministic results (for any set of peers) - implement 'SUPPORT_DELAYS' - consider re-issue GSF_dht_lookup_ after non-DHT reply received - implement multi-peer FS performance tests + gauger them! + insert + download + search * GNUNET-GTK: [CG] - figure out where in the GUI we should show active upload operations and allow aborts - handle events: + search error + publish error * Determine RC bugs and fix those (release should have no known real bugs) 0.9.0: * new webpage: - write chapter on DHT/block [Nate] - make a NICE download page * big code review * Determine RC bugs and fix those (release should have no known real bugs) 0.9.1: * TRANSPORT: [MW] - 'TransmitFunction' requires plugins to have "unbounded" queue (or at least queue of size > 2), might be better to have at MOST one message pending per plugin/target and only send the next one after the continuation was called (or use 'notify_transmit_ready-style API?) - WiFi transport backend [DB] - 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! - need to periodically probe latency/transport cost changes & possibly switch transport * DATASTORE: [CG] - check indexes / SQL for performance * DV: [Nate?] - proper bandwidth allocation - performance tests * PEERINFO: - merge multiple HELLOs of the same peer in the transmission queue (theoretically reduces overhead; bounds message queue size) - merge multiple iteration requests over "all" peers in the queue (theoretically reduces overhead; bounds messgae queue size) * STATISTICS: - should use BIO instead of mmap * FS: [CG] - Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009) - use different queue prioritization for probe-downloads vs. normal downloads - re-implement gnunet-auto-share - implement 'GNUNET_FS_file_information_create_from_directory', avoiding code duplication with gnunet-gtk's similar code (!) * GNUNET-GTK: [CG] - add tool bar - do meaningful update to status line (starting up, peer running, #connections, shutdown, ...) - add progress dialog for 'add_dir_at_iter' scan (can take a while...) - NS list in search dialog should use colors to offset our own namespaces from the others - right-clicking on NS list in search dialog should open menu that allows * viewing full meta data * deletion of namespace info - implement unindex operation (use dialog with all indexed files for selection) - finish publish dialog details: + normalize keywords (edit subdialog) - implement download by URI dialog; figure out where to display those downloads! - add combo box to select desired mime type for search * ARM: [CG/Safey] - better tracking of which config changes actually need to cause process restarts by ARM. - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?) - discover dependencies between services * MONKEY: [Safey] - better crash management (attach debugging support, capture and analyze debug output, detect random vs. deterministic crashes) - '-m EMAIL' option for alternative e-mail TO - '-f FILENAME' option to write report to file instead of e-mail (for testing!) 0.9.2: * PEERINFO: [NN] - 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 * 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?) - WiFi transport backend * nice signal strength adjustment [MW] * energy cost in ATS [MW] * BLOCKS: - testcase would be nice - generic block support for DHT * STATISTICS: - test notification-based statistics API - implement statistics GUI (=> start from gnunet-gtk by button!) * PEERINFO: [NN] - move peerinfo to new GUI (=> start from gnunet-gtk by button!) - extend peer dialog with green-yellow-red connectivity status lights - extend peer dialog with country flags and names 0.9.3: * SMTP transport backend: - sending (SMTP/SMTPS) - receiving (IMAP/IMAPS/POP?) - rate limiting - improved batching - resource limit integration with ATS * VPN [PT] - TCP entry/exit - internal services - integration with DHT routing - optimized routes (beyond DHT/DV) - "DNS" .gnunet