I noticed with znc 1.7.0 a new unintended (?) behavior with the new crypt-prefix mechanism.
Status prefix: *
Crypt prefix: .
On connect to a znc session with an encrypted channel I get an initial RPL_NAMREPLY (numeric 353) where my user is listed twice: once with the crypt prefix (.) and once in regular notation. When I manually request a names list (/names #channel), I get the proper RPL_NAMREPLY with only one user (without prefix). This is a problem as IRC clients populate the user list by evaluating the RPL_NAMREPLY thus showing a user not really in the channel.
Example:
On first connection to session: :port80b.se.quakenet.org 353 MyNick @ #channel :.MyNick!ident@hostname @Q @MyNick!ident@hostname
I suspect the first RPL_NAMREPLY is generated by znc and the consecutive ones are coming from the real IRC server. You can see the full hostmask on the initial RPL_NAMREPLY but any replies after that only show the nickname.
Might be connected to #1553 as it is happening in the same channel and znc instance with enabled playback.
I noticed with znc 1.7.0 a new unintended (?) behavior with the new crypt-prefix mechanism.
Status prefix: *
Crypt prefix: .
On connect to a znc session with an encrypted channel I get an initial RPL_NAMREPLY (numeric 353) where my user is listed twice: once with the crypt prefix (.) and once in regular notation. When I manually request a names list (/names #channel), I get the proper RPL_NAMREPLY with only one user (without prefix). This is a problem as IRC clients populate the user list by evaluating the RPL_NAMREPLY thus showing a user not really in the channel.
Example:
On first connection to session:
`:port80b.se.quakenet.org 353 MyNick @ #channel :.MyNick!ident@hostname @Q @MyNick!ident@hostname`
On manual /names #channel request:
`:port80b.se.quakenet.org 353 MyNick @ #channel :@MyNick @Q`
I suspect the first RPL_NAMREPLY is generated by znc and the consecutive ones are coming from the real IRC server. You can see the full hostmask on the initial RPL_NAMREPLY but any replies after that only show the nickname.
Might be connected to #1553 as it is happening in the same channel and znc instance with enabled playback.
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:331694551 -->
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.
I noticed with znc 1.7.0 a new unintended (?) behavior with the new crypt-prefix mechanism.
Status prefix: *
Crypt prefix: .
On connect to a znc session with an encrypted channel I get an initial RPL_NAMREPLY (numeric 353) where my user is listed twice: once with the crypt prefix (.) and once in regular notation. When I manually request a names list (/names #channel), I get the proper RPL_NAMREPLY with only one user (without prefix). This is a problem as IRC clients populate the user list by evaluating the RPL_NAMREPLY thus showing a user not really in the channel.
Example:
On first connection to session:
:port80b.se.quakenet.org 353 MyNick @ #channel :.MyNick!ident@hostname @Q @MyNick!ident@hostnameOn manual /names #channel request:
:port80b.se.quakenet.org 353 MyNick @ #channel :@MyNick @QI suspect the first RPL_NAMREPLY is generated by znc and the consecutive ones are coming from the real IRC server. You can see the full hostmask on the initial RPL_NAMREPLY but any replies after that only show the nickname.
Might be connected to #1553 as it is happening in the same channel and znc instance with enabled playback.
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