i don't think that is exclusive to zabbix and those using 'admin' as a
password deserve 'some weirdness' imho.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving
Thanks for replying, I guess I will add `notes:` section to zabbix
documentation fragment stating that using default Admin password is not
recommended and to expect weird output.
On Wednesday, August 14, 2019 at 2:55:41 PM UTC+2, Brian Coca wrote:
>
> if no_log could be bypassed and runtime,
if no_log could be bypassed and runtime, it would trigger a CVE ... so
the way to test the modules is to disable no_log in the module code
itself.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe
Hi,
I've been searching for ways to bypass no_log option for specific module
output, but with no luck so far. To my understanding, providing no_log for
at least one argument in argument_spec makes every module output containing
value of such argument to be altered.
This makes trouble for
