adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-10-31 01:32:02 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

Crypt: wrong echo-message for outgoing messages #891

New Issue
Open
opened 2026-10-05 04:51:05 +02:00 by adam · 2 comments
adam commented 2026-10-05 04:51:05 +02:00
Owner
Copy link
Copy source

Related to: e30dfdc and #1481

I'm using TheLounge, which is reacting on the echo-message and putting it into my view/timeline.
Right now when I write something, I get the encrypted value back as reply. I would've expected to get the unencrypted message back (the same one, that I actually have written).

testmessage: PRIVMSG #testing TEST
echo-reply: @time=2019-01-07T10:18:07.531Z :keigel2001!~keigel2k1@p... PRIVMSG #testing :+OK *ABKW3kFF8J2Jcku9MqSalA==

expected echo-reply: @time=2019-01-07T10:18:07.531Z :keigel2001!~keigel2k1@p... PRIVMSG #testing :TEST

Related to: e30dfdc and #1481 I'm using TheLounge, which is reacting on the echo-message and putting it into my view/timeline. Right now when I write something, I get the encrypted value back as reply. I would've expected to get the unencrypted message back (the same one, that I actually have written). **testmessage:** `PRIVMSG #testing TEST` **echo-reply:** `@time=2019-01-07T10:18:07.531Z :keigel2001!~keigel2k1@p... PRIVMSG #testing :+OK *ABKW3kFF8J2Jcku9MqSalA==` **expected echo-reply:** `@time=2019-01-07T10:18:07.531Z :keigel2001!~keigel2k1@p... PRIVMSG #testing :TEST` <!-- github-sync-id:396745614 -->
adam commented 2026-10-05 04:51:06 +02:00
Author
Owner
Copy link
Copy source

That's an interesting case to consider, the echo-message specification states:

If servers apply any modifications to these messages, they MUST send the final version of the message back to the originating client. (https://ircv3.net/specs/extensions/echo-message-3.2.html)

The wording of MUST is unfortunate here, perhaps it would make sense to try and get echo-message specification adjusted to be a SHOULD or similiar to allow bouncers to not provide the final version of the message in some cases such as if it is encrypted and won't make sense to to the client.

That's an interesting case to consider, the echo-message specification states: > If servers apply any modifications to these messages, they MUST send the final version of the message back to the originating client. (https://ircv3.net/specs/extensions/echo-message-3.2.html) The wording of `MUST` is unfortunate here, perhaps it would make sense to try and get echo-message specification adjusted to be a `SHOULD` or similiar to allow bouncers to not provide the final version of the message in some cases such as if it is encrypted and won't make sense to to the client. <!-- github-comment-id:667694649 -->
adam commented 2026-10-05 04:51:07 +02:00
Author
Owner
Copy link
Copy source

Just encountered this, for anyone else having problems with this, until a solution is ready, it can temporarily be mitigated with DisableClientCap = echo-message in znc.conf

(Requires znc >= 1.10.0)

Just encountered this, for anyone else having problems with this, until a solution is ready, it can temporarily be mitigated with `DisableClientCap = echo-message` in znc.conf (Requires znc >= 1.10.0) <!-- github-comment-id:3134582234 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#891