With the current version (1.7.0) of znc the backlog playback does not decrypt the following events:
Topics from any user (buffextras)
Message from myself to the channel
Action from myself to the channel
Notice from myself to the channel
How to reproduce:
Activate modules "crypt" and "buffextras", encrypt a channel, do any of the described points above, /msg *playback PLAY #channel 3600
With the current version (1.7.0) of znc the backlog playback does not decrypt the following events:
* Topics from any user (buffextras)
* Message from myself to the channel
* Action from myself to the channel
* Notice from myself to the channel
How to reproduce:
Activate modules "crypt" and "buffextras", encrypt a channel, do any of the described points above, /msg *playback PLAY #channel 3600
Info:
Linux 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 GNU/Linux
ZNC 1.7.0 - https://znc.in
IPv6: yes, SSL: yes, DNS: threads, charset: yes, i18n: no, build: autoconf
<!-- github-sync-id:330901187 -->
@DarthGandalf In this particular case, all users involved are on the same instance of znc and therefore using the same crypt-module.
@DarthGandalf In this particular case, all users involved are on the same instance of znc and therefore using the same crypt-module.
<!-- github-comment-id:395987969 -->
I just noticed that it doesn't only affect the backlog:
When two clients are connected to the same znc-instance and client a sends text to a channel that is encrypted with crypt, client b receives the message in encrypted form (e.g. +OK *2segUMSMhvPs...).
I just noticed that it doesn't only affect the backlog:
When two clients are connected to the same znc-instance and client a sends text to a channel that is encrypted with crypt, client b receives the message in encrypted form (e.g. +OK *2segUMSMhvPs...).
<!-- github-comment-id:396608496 -->
I just noticed that it doesn't only affect the backlog:
When two clients are connected to the same znc-instance and client a sends text to a channel that is encrypted with crypt, client b receives the message in encrypted form (e.g. +OK *2segUMSMhvPs...).
Same here. Multiple clients does not work properly with Crypt module, as my own message are shown encrypted on the other client and vice versa.
> I just noticed that it doesn't only affect the backlog:
> When two clients are connected to the same znc-instance and client a sends text to a channel that is encrypted with crypt, client b receives the message in encrypted form (e.g. +OK *2segUMSMhvPs...).
Same here. Multiple clients does not work properly with Crypt module, as my own message are shown encrypted on the other client and vice versa.
<!-- github-comment-id:455585065 -->
> Same here. Multiple clients does not work properly with Crypt module, as my own message are shown encrypted on the other client and vice versa.
I think this is a duplicate of #1629.
<!-- github-comment-id:455644646 -->
I am seeing this issue with 1.7.5+deb4 from Ubuntu 20.04.
Is there a workaround? Or possibly another module that can provide encrypted communication in an otherwise public channel?
I am seeing this issue with 1.7.5+deb4 from Ubuntu 20.04.
Is there a workaround? Or possibly another module that can provide encrypted communication in an otherwise public channel?
<!-- github-comment-id:659438539 -->
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.
With the current version (1.7.0) of znc the backlog playback does not decrypt the following events:
How to reproduce:
Activate modules "crypt" and "buffextras", encrypt a channel, do any of the described points above, /msg *playback PLAY #channel 3600
Info:
Linux 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 GNU/Linux
ZNC 1.7.0 - https://znc.in
IPv6: yes, SSL: yes, DNS: threads, charset: yes, i18n: no, build: autoconf
Duplicate of #1532 ?
@Cizzle
@DarthGandalf In this particular case, all users involved are on the same instance of znc and therefore using the same crypt-module.
Don't think it's a duplicate. Would have to test but as I don't actively use znc I can't put an ETA on that.
I just noticed that it doesn't only affect the backlog:
When two clients are connected to the same znc-instance and client a sends text to a channel that is encrypted with crypt, client b receives the message in encrypted form (e.g. +OK *2segUMSMhvPs...).
Same here. Multiple clients does not work properly with Crypt module, as my own message are shown encrypted on the other client and vice versa.
I think this is a duplicate of #1629.
I am seeing this issue with 1.7.5+deb4 from Ubuntu 20.04.
Is there a workaround? Or possibly another module that can provide encrypted communication in an otherwise public channel?