On UnderNet IRC, the channel key is only shown when someone is op'd in the channel.
ZNC gets the channel modes from raw message 324 which sends the channel modes when op'd in the channel.
If the channel is set with mode +tnsk key, and raw message 324 sends the modes in this order, +knst, it just shows +knst *.
If it sends raw message 324 and the modes are in this order, +stnk, it shows +stnk key.
Version 1.4
User Modules Loaded:
chansaver
controlpanel
perform
webadmin
Network Modules Loaded:
autoop
chansaver
keepnick
perform
simple_away
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/7645958-undernet-irc-channel-key-issue?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:53977190 -->
I think this is duplicate of (https://github.com/znc/znc/issues/709 which is duplicate of) https://github.com/znc/znc/issues/674.
<!-- github-comment-id:69485485 -->
It's not a duplicate of #709 or #674. It has nothing to do with being disconnected, or losing the channel key. This is to do with ZNC not reading the channel key when receiving raw message 324 in certain cases.
It's not a duplicate of #709 or #674. It has nothing to do with being disconnected, or losing the channel key. This is to do with ZNC not reading the channel key when receiving raw message 324 in certain cases.
<!-- github-comment-id:69486797 -->
I figured out at least one scenario where the channel key wasn't saved as appropriate. See https://github.com/znc/znc/pull/1089 for details.
<!-- github-comment-id:139858526 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On UnderNet IRC, the channel key is only shown when someone is op'd in the channel.
ZNC gets the channel modes from raw message 324 which sends the channel modes when op'd in the channel.
If the channel is set with mode +tnsk key, and raw message 324 sends the modes in this order, +knst, it just shows +knst *.
If it sends raw message 324 and the modes are in this order, +stnk, it shows +stnk key.
Version 1.4
User Modules Loaded:
chansaver
controlpanel
perform
webadmin
Network Modules Loaded:
autoop
chansaver
keepnick
perform
simple_away
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
I think this is duplicate of (https://github.com/znc/znc/issues/709 which is duplicate of) https://github.com/znc/znc/issues/674.
It's not a duplicate of #709 or #674. It has nothing to do with being disconnected, or losing the channel key. This is to do with ZNC not reading the channel key when receiving raw message 324 in certain cases.
I just tried ZNC 1.6.0
The bug still exists.
I figured out at least one scenario where the channel key wasn't saved as appropriate. See https://github.com/znc/znc/pull/1089 for details.