The whitelist command currently accepts multiple client status arguments (e.g., whitelist 1 cs/old cs/active) and uses the last status provided. This behavior is unintended. The command should accept only one status argument and reject commands with multiple status inputs to prevent ambiguity.
The whitelist command currently accepts multiple client status arguments (e.g., whitelist 1 cs/old cs/active) and uses the last status provided. This behavior is unintended. The command should accept only one status argument and reject commands with multiple status inputs to prevent ambiguity.