Mirrors/ansible-collection-famedly-base
2
0
Fork 0
mirror of https://github.com/famedly/ansible-collection-base synced 2024-09-20 06:11:58 +00:00
Code Issues Projects Releases Packages Wiki Activity

chore: remove trailing whitespace

Browse source
This commit is contained in:
Jan Christian Grünhage 2021-01-22 21:10:00 +01:00
parent a18c544492
commit cf282336b2
No known key found for this signature in database
GPG key ID: 6594C449C633D10C
3 changed files with 12 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
roles/redis/templates/redis.conf.j2
View file

@ -142,7 +142,7 @@ tcp-keepalive 300
# server to connected clients, masters or cluster peers. These files should be
# PEM formatted.
#
# tls-cert-file redis.crt
# tls-cert-file redis.crt
# tls-key-file redis.key
# Configure a DH parameters file to enable Diffie-Hellman (DH) key exchange:
@ -763,8 +763,8 @@ replica-priority 100
# ACL LOG
#
# The ACL Log tracks failed commands and authentication events associated
# with ACLs. The ACL Log is useful to troubleshoot failed commands blocked
# by ACLs. The ACL Log is stored in memory. You can reclaim memory with
# with ACLs. The ACL Log is useful to troubleshoot failed commands blocked
# by ACLs. The ACL Log is stored in memory. You can reclaim memory with
# ACL LOG RESET. Define the maximum entry length of the ACL Log below.
acllog-max-len 128
@ -1322,18 +1322,18 @@ lua-time-limit 5000
# cluster-replica-no-failover no
# This option, when set to yes, allows nodes to serve read traffic while the
# the cluster is in a down state, as long as it believes it owns the slots.
# the cluster is in a down state, as long as it believes it owns the slots.
#
# This is useful for two cases. The first case is for when an application
# This is useful for two cases. The first case is for when an application
# doesn't require consistency of data during node failures or network partitions.
# One example of this is a cache, where as long as the node has the data it
# should be able to serve it.
# should be able to serve it.
#
# The second use case is for configurations that don't meet the recommended
# three shards but want to enable cluster mode and scale later. A
# The second use case is for configurations that don't meet the recommended
# three shards but want to enable cluster mode and scale later. A
# master outage in a 1 or 2 shard configuration causes a read/write outage to the
# entire cluster without this option set, with it set there is only a write outage.
# Without a quorum of masters, slot ownership will not change automatically.
# Without a quorum of masters, slot ownership will not change automatically.
#
# cluster-allow-reads-when-down no

4
roles/ssh/tasks/main.yml
View file

@ -46,7 +46,7 @@
<<: *sshd_config_args
regexp: "^#?Protocol"
line: "Protocol 2"
insertafter: &cipher_after "^# Ciphers and keying"
insertafter: &cipher_after "^# Ciphers and keying"
notify: reload sshd
- name: Disallow X11-Forwarding
@ -91,7 +91,7 @@
<<: *sshd_config_args
regexp: '^#?MACs'
line: "MACs {{ ssh_preset.allowed_macs|join(',') }}"
insertafter: *cipher_after
insertafter: *cipher_after
notify: reload sshd
- name: Only allow reasonably secure hostkey algorithms

2
roles/ssh/vars/main.yml
View file

@ -8,7 +8,7 @@ ssh_secure_presets:
- diffie-hellman-group14-sha256
allowed_ciphers: "{{ [ 'chacha20-poly1305@openssh.com' ] + ssh_bsi_recommended_presets.allowed_ciphers }}"
allowed_macs:
- hmac-sha2-512-etm@openssh.com
- hmac-sha2-512-etm@openssh.com
- hmac-sha2-256-etm@openssh.com
- umac-128-etm@openssh.com
allowed_hostkey_algos: