ansible-sshd/templates/sysconfig.j2

{{ ansible_managed | comment }}
{{ "willshersystems:ansible-sshd" | comment(prefix="", postfix="") }}
{% if __sshd_sysconfig_supports_crypto_policy %}
{%   if sshd_sysconfig_override_crypto_policy | bool %}
CRYPTO_POLICY=
{%   endif %}
{% endif %}

{% if __sshd_sysconfig_supports_use_strong_rng %}
SSH_USE_STRONG_RNG={{ sshd_sysconfig_use_strong_rng }}
{% endif %}
Use {{ ansible_managed \| comment }} to fix multi-line ansible_managed BZ#2006230, BZ#2006231, BZ#2006233 2021-09-21 11:41:17 +02:00			`{{ ansible_managed \| comment }}`
Fingerprint ansible-sshd managed config files - Add repo and role name to the generated config files. # willshersystems:ansible-sshd Signed-off-by: Noriko Hosoi <nhosoi@redhat.com> 2023-03-29 19:28:38 +02:00			`{{ "willshersystems:ansible-sshd" \| comment(prefix="", postfix="") }}`
Add support for sysconfig on Fedora/RHEL This is useful for opting out from system-wide cryto policy for SSH or configuring advanced use case (strong RNG seed). Fixes: #141 2020-10-06 21:11:35 +02:00			`{% if __sshd_sysconfig_supports_crypto_policy %}`
Ensure values are cast to correct type https://github.com/willshersystems/ansible-sshd/issues/188 This shouldn't be necessary, but there seems no way to guarantee using a version of Jinja which doesn't have this problem. In addition - it is not good practice to compare values to `true` or `false` - instead, just ensure the value is a `bool` type and evaluate in a boolean context. 2022-08-11 18:47:46 +02:00			`{% if sshd_sysconfig_override_crypto_policy \| bool %}`
Add support for sysconfig on Fedora/RHEL This is useful for opting out from system-wide cryto policy for SSH or configuring advanced use case (strong RNG seed). Fixes: #141 2020-10-06 21:11:35 +02:00			`CRYPTO_POLICY=`
			`{% endif %}`
			`{% endif %}`

			`{% if __sshd_sysconfig_supports_use_strong_rng %}`
			`SSH_USE_STRONG_RNG={{ sshd_sysconfig_use_strong_rng }}`
			`{% endif %}`