Bug

Thu Sep 18 10:48:08 2025 UTC

Ladies and gentlemen,

I'm afraid I've got a serious bug or flow within the association establishing protocol logic, which manifestates as repeated failed decrypting association request from message in the log. The problem is that I don't understand why this happens. Yesterday's evening I had it on my node, it was repeatedly complaining about several peers' requests, and restarting the daemon didn't change anything. Today I tried to add more debug messages to the daemon; this caused me to restart both the node and those of my own peers which were involved, and guess what happend — the problem disappeared and I can't cause it to happen again. Those of you who has some expirience in programming might know this is the most terrible types of bug.

Anyway, all we can do now is to wait for it to happen again. This post is just to keep you all informed, specially those of you who now try running nodes.


anonymous

From Yury K. (unverified) Thu Sep 18 14:44:11 2025 UTC

pencil

Сaught it

I think I caught it.

Added some additional debug info:

diff --git a/src/fsrv_rx.c b/src/fsrv_rx.c
index 42c0aa9..b95c8fc 100644
--- a/src/fsrv_rx.c
+++ b/src/fsrv_rx.c
@@ -909,6 +909,8 @@ static void handle_associate_request(struct feda_udp_receiver *feda_rx,
     unsigned char point_pubkey[public_key_size];
     unsigned char signed_stuff[public_key_size + 4 + cipher_nonce_used];
 
+    servlog_message(srvl_debug, "assoc req payload: %s", hexdata2a(payload, payload_len));//xxx
+
     peer = get_peer_rec(feda_rx, ip, port, 1);
     fp = peer->userdata;

and got this:

the_housekeeping_hook called                                                                                                                                                                                                                  
UDP (378 bytes) from 132.145.107.156:65242 [e3969f5ebf...]                                                                                                                                                                                    
plain dgram; cmd a5                                                                                                                                                                                                                           
assoc req payload: 9f5ebf8f983ef7e722f580d0e5389274a259a88ba5c45e4c12dc5e007964f92718c2d2a0b49649f0dd053291a24302d8e4ea93297afb7aeaa1a183fa283b8b0e4e5f7cdf9ce532c85db57d9753cc7d07493fbd9ced0fe48ab8862f4f9a334295f6f417e010094aedb35c0953491
8f97a65a2779e5b379b420e0f7b7197ab97b14bdfd0c596fdd6e84f697c656d12c4e7c81bafa1065c648c4a490ba058910c48957f398e23053653b7d2c6213d7a0a7b2188c59ac1edb748dd2f52255582d45baa1b87fd7a81123d457ab13053cc5f119184e69aac1147a13b232ebdcd695c3fdb4de310a
4c04764a0d2864537b0445583174cc29aa45796d5a5a261e161b17fdcf5cc60b2b09ca6d775cb0619b34bcf95a315a0553e93272ac04c289ecf0244d4bfece8b2a06623ea392b2620da326547a91ad3445fbe62666e179995b5db78e27d6bd881e594c4834a02d33bd785e5a9aea69a9ed062836f028e0
b92f76d2e46c64c7b3172d367fd6ca1634e9795e41e4cc6f9a08afbfc                                                                                                                                                                                     
peer 132.145.107.156:65242 object address 2e237ea0                                                                                                                                                                                            
failed decrypting association request from 132.145.107.156:65242                                                                                                                                                                              
sending plaintext dgram (cmd=e8) to 132.145.107.156:65242                                                                                                                                                                                     
sent 128 bytes to 132.145.107.156:65242 [f79f061342...]; 0                                                                                                                                                                                    

No other changes were made on my side.

admin.jpg's userpic

From Andrey Stolyarov profile Thu Sep 18 15:27:34 2025 UTC in reply to this comment

pencil

Re: Сaught it

I'm a bit confused: what information should I gain here? The payload is just some cryptgraphic data (e.g., it starts with the sender's kex/temporary public key), so printing it doesn't make much sense; as of the bug itself, well, I know it exists, I only don't know how to reproduce it more or less reliably.

no userpic

From feriman profile Thu Sep 18 21:44:48 2025 UTC in reply to this comment

pencil

Re: Re: Сaught it

Yury, please tell us, how you reproduce it on my node?

anonymous

From Yury K. (unverified) Fri Sep 19 11:10:30 2025 UTC in reply to this comment

pencil

Re: Re: Сaught it

Yeah, you're right. I rushed a bit with the comment, sorry.