With #343 there is the concept of client IDs, which can share the same user in ZNC. However all of the clients share the same credentials, which makes it a PITA when there is a compromise. It would be nice, if different client IDs could use different passwords, so loosing a mobile phone for instance, does not require me to change the password on all other devices.
With #343 there is the concept of client IDs, which can share the same user in ZNC. However all of the clients share the same credentials, which makes it a PITA when there is a compromise. It would be nice, if different client IDs could use different passwords, so loosing a mobile phone for instance, does not require me to change the password on all other devices.
<!-- github-sync-id:297042876 -->
Something similar could be achieved by a workaround proposed here. Basically you create new users for each client, which connect back on localhost to a master user.
Something similar could be achieved by a workaround proposed [here](https://blog.jay2k1.com/2016/02/04/how-to-configure-znc-backlog-for-multiple-clients/). Basically you create new users for each client, which connect back on localhost to a master user.
<!-- github-comment-id:365560822 -->
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 #343 there is the concept of client IDs, which can share the same user in ZNC. However all of the clients share the same credentials, which makes it a PITA when there is a compromise. It would be nice, if different client IDs could use different passwords, so loosing a mobile phone for instance, does not require me to change the password on all other devices.
Something similar could be achieved by a workaround proposed here. Basically you create new users for each client, which connect back on localhost to a master user.