X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=BUGS;h=67c7b407f85f7c585656e5f95d5cb9ea0a44ab78;hb=e07f6311788307d06d907952a8686add4f0cc16b;hp=1d9398c9b2ad2a582f3f36bc3abd1be51952ca32;hpb=6776eda81f7712d24b4a54943642cf90af7ee4d8;p=oweals%2Fgnunet.git diff --git a/BUGS b/BUGS index 1d9398c9b..67c7b407f 100644 --- a/BUGS +++ b/BUGS @@ -36,17 +36,6 @@ sane end-user should care about this codebase yet anyway. a way to easily "veto" addresses off the list! => If MiM attacker uses vetoed address, blacklist the specific IP for the presumed neighbour! - - not sure current way of doing ACKs works well-enough - with unreliable transports where the ACK maybe lost; - the "is_new" check would then possibly prevent future - ACKs to be delivered, all while we're happily - receiving messages from that peer! Worse, the other - peer won't generate another ACK since it thinks we're - connected just fine... - Key questions: - + How necessary is ACKing in the first place? (alternatives?) - + Should we transmit ACKs in response to every HELLO? (would that - fully address the problem?) - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used * FS: @@ -84,14 +73,12 @@ sane end-user should care about this codebase yet anyway. - integrate all options into "config.scm" - change config-file writing to exclude options set to default values * ARM: - - implement exponential back-off for service restarts - better tracking of which config changes actually need to cause process restarts by ARM. - - have way to specify dependencies between services (to manage ARM restarts better) -* CORE: - - test case (test_core_api) hangs for a while (some timeout task not killed somewhere?) - - [./core/gnunet-service-core.c:469]: (style) struct or union member 'Neighbour::message_queue_size' is never used - - [./core/test_core_api_start_only.c:50]: (style) struct or union member 'PeerContext::id' is never used - + - 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? * HTTPS transport - Better SSL-support for MHD - https integration