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.
From Yury K. (unverified) Thu Sep 18 14:44:11 2025 UTC
Сaught it
I think I caught it.
Added some additional debug info:
and got this:
No other changes were made on my side.
reply
From Andrey Stolyarov
Thu Sep 18 15:27:34 2025
UTC
in reply to
this comment
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.
reply
From feriman
Thu Sep 18 21:44:48 2025
UTC
in reply to
this comment
Re: Re: Сaught it
Yury, please tell us, how you reproduce it on my node?
reply
From Yury K. (unverified) Fri Sep 19 11:10:30 2025 UTC in reply to this comment
Re: Re: Сaught it
Yeah, you're right. I rushed a bit with the comment, sorry.
reply