Please allow to disable "DEBUG mode" warning at connect. #841

New Issue

2026-10-05T04:48:06+02:00

adam commented

2026-10-05 04:48:06 +02:00

Recent znc versions will send you a private message from *status upon connecting to the bouncer if it's running in debug mode. I understand the reason for this message but please add an option to (optionally) disable this warning (config, command line, etc.). Every time I connect to the bouncer my client is telling me I have new private messages which is really annoying.

I'm the only user on my bouncer and I have root access anyway. If an admin had bad intentions on a multi user instance, they could simply remove the warning and compile znc themself. There are better options if you want to snoop on your users.

I'm running znc in debug mode on purpose since debugging connection issues without stdout is really annoying and I don't want to have to restart znc just to enable debugging and then restart it again to disable it.

Commit that introduced this feature: https://github.com/znc/znc/commit/ab501767a18eece2b3c553868d0c7cfbe496d658

Recent znc versions will send you a private message from *status upon connecting to the bouncer if it's running in debug mode. I understand the reason for this message but please add an option to (optionally) disable this warning (config, command line, etc.). Every time I connect to the bouncer my client is telling me I have new private messages which is really annoying. I'm the only user on my bouncer and I have root access anyway. If an admin had bad intentions on a multi user instance, they could simply remove the warning and compile znc themself. There are better options if you want to snoop on your users. I'm running znc in debug mode on purpose since debugging connection issues without stdout is really annoying and I don't want to have to restart znc just to enable debugging and then restart it again to disable it. Commit that introduced this feature: https://github.com/znc/znc/commit/ab501767a18eece2b3c553868d0c7cfbe496d658

adam closed this issue

2026-10-05 04:48:06 +02:00

adam commented

2026-10-05 04:48:07 +02:00

Why are you running your instance in debug mode?

Why are you running your instance in debug mode?

adam commented

2026-10-05 04:48:08 +02:00

@magnum7385

I'm running znc in debug mode on purpose since debugging connection issues without stdout is really annoying and I don't want to have to restart znc just to enable debugging and then restart it again to disable it.

@magnum7385 > I'm running znc in debug mode on purpose since debugging connection issues without stdout is really annoying and I don't want to have to restart znc just to enable debugging and then restart it again to disable it.

adam commented

2026-10-05 04:48:09 +02:00

Thanks, @psychon

Thanks, @psychon

adam commented

2026-10-05 04:48:09 +02:00

@Zarthus any objections to reverting that commit?

@Zarthus any objections to reverting that commit?

adam commented

2026-10-05 04:48:10 +02:00

@DarthGandalf I have objections.

https://github.com/znc/znc/issues/1370 is the real solution to this problem.

He can ignore/filter the status query if he doesn't want it. The entire purpose of the message is to be annoying. (The feature wasn't introduced to avoid people snooping on your znc; in general you shouldn't be on a bouncer hosted by someone you don't trust. This feature is for transperancy, users SHOULD know that debug mode is enabled when they are connected.)

In the end, if you're running znc in debug mode permanently, there's something wrong with the software; not with the notification that tells you about it. (and I think #1370 is the fix for this)

PS. Nice Sif avatar, Lupinus

PSS. Alternatively we could improve the behaviour of this commit, show it only once per user per hour or so.

@DarthGandalf I have objections. https://github.com/znc/znc/issues/1370 is the real solution to this problem. He can ignore/filter the status query if he doesn't want it. The entire purpose of the message is to be annoying. (The feature wasn't introduced to avoid people snooping on your znc; in general you shouldn't be on a bouncer hosted by someone you don't trust. This feature is for transperancy, users SHOULD know that debug mode is enabled when they are connected.) In the end, if you're running znc in debug mode permanently, there's something wrong with the software; not with the notification that tells you about it. (and I think #1370 is the fix for this) PS. Nice Sif avatar, Lupinus PSS. Alternatively we could improve the behaviour of this commit, show it only once per user per hour or so.

adam commented

2026-10-05 04:48:11 +02:00

Ability to turn debugging on at runtime (#1370) doesn't make such
notification useful.

2018-05-29 11:24 GMT+01:00 Jos Ahrens notifications@github.com:

@DarthGandalf https://github.com/DarthGandalf I have objections.

#1370 https://github.com/znc/znc/issues/1370 is the real solution to
this problem.

He can ignore/filter the status query if he doesn't want it.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/znc/znc/issues/1541#issuecomment-392728394, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAT15JwS8yTYET3Lu7Y4c-05isWjPl3gks5t3SHCgaJpZM4UP_EI
.

Ability to turn debugging on at runtime (#1370) doesn't make such notification useful. 2018-05-29 11:24 GMT+01:00 Jos Ahrens <notifications@github.com>: > @DarthGandalf <https://github.com/DarthGandalf> I have objections. > > #1370 <https://github.com/znc/znc/issues/1370> is the real solution to > this problem. > > He can ignore/filter the status query if he doesn't want it. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/znc/znc/issues/1541#issuecomment-392728394>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAT15JwS8yTYET3Lu7Y4c-05isWjPl3gks5t3SHCgaJpZM4UP_EI> > . >

adam commented

2026-10-05 04:48:11 +02:00

Yes it does, if it's enabled while you are connected.

The feature itself would probably also broadcast to all connected clients that "debug mode is now being turned on" and "debug mode is now being turned off".

Yes it does, if it's enabled while you are connected. The feature itself would probably also broadcast to all connected clients that "debug mode is now being turned on" and "debug mode is now being turned off".

adam commented

2026-10-05 04:48:12 +02:00

With https://github.com/znc/znc/pull/1556 this should now be mitigated, run znc like znc --foreground > out.log or using systemd and then toggle the debug mode when you want to debug connections. (or start it in debug mode and turn it off when you're done with it)

With https://github.com/znc/znc/pull/1556 this should now be mitigated, run znc like `znc --foreground > out.log` or using systemd and then toggle the debug mode when you want to debug connections. (or start it in debug mode and turn it off when you're done with it)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#841