This is an issue because ZNC's startup messages could end up somewhere less secure than ZNC's config file, without realizing it, eg syslog, journal, email, depending on how ZNC is started. ZNC already doesn't send the server password during ListServers as of 1.7.0, so the same should be applied to startup messages.
e.g.:
```
$ znc
[ .. ] Checking for list of available modules...
[ .. ] Opening config [/home/dwfreed/.znc/configs/znc.conf]...
[ .. ] Loading global module [webadmin]...
[ .. ] Binding to port [+6697] on host [::1]...
[ .. ] Binding to port [+6697] on host [127.0.0.1]...
[ ** ] Loading user [dwfreed]
[ ** ] Loading network [NETWORK]
[ .. ] Adding server [::1 +31459 PASSWORD]...
[ .. ] Loading user module [chansaver]...
[ .. ] Loading user module [controlpanel]...
[ .. ] Loading user module [buffextras]...
[ .. ] Forking into the background...
[ >> ] [pid: 9127]
[ ** ] ZNC 1.7.1 - https://znc.in
```
This is from: https://github.com/znc/znc/blob/2f4b158fd1d1c03eee5f73777bcb55b0d6c535b5/src/IRCNetwork.cpp#L488
This is an issue because ZNC's startup messages could end up somewhere less secure than ZNC's config file, without realizing it, eg syslog, journal, email, depending on how ZNC is started. ZNC already doesn't send the server password during ListServers as of 1.7.0, so the same should be applied to startup messages.
<!-- github-sync-id:364455660 -->
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.
e.g.:
This is from: https://github.com/znc/znc/blob/2f4b158fd1d1c03eee5f73777bcb55b0d6c535b5/src/IRCNetwork.cpp#L488
This is an issue because ZNC's startup messages could end up somewhere less secure than ZNC's config file, without realizing it, eg syslog, journal, email, depending on how ZNC is started. ZNC already doesn't send the server password during ListServers as of 1.7.0, so the same should be applied to startup messages.