Jérémy Dubois
78686b8730
Fix #34 again After some discussions, with actually need two separates groups : - One group for ssh access (evobsd_ssh_group) - One group for sudo/doas access (evobsd_sudo_group) We won't need any client group. A client user will be added to the ssh group, so that we won't have to think about what specific group a user need to be added in.
39 lines
1.2 KiB
YAML
39 lines
1.2 KiB
YAML
---
|
|
########################################################
|
|
## Edit and uncomment to overwrite the default values ##
|
|
########################################################
|
|
|
|
# ntpd_servers:
|
|
# - "ntp.evolix.net"
|
|
#
|
|
# general_alert_email: "root@localhost"
|
|
# general_technical_realm: "example.com"
|
|
#
|
|
# evomaintenance_realm: "example.com"
|
|
# evomaintenance_alert_email:
|
|
# "evomaintenance-{{ inventory_hostname }}@{{ evomaintenance_realm }}"
|
|
# evomaintenance_hostname:
|
|
# "{{ inventory_hostname }}.{{ general_technical_realm }}"
|
|
# evomaintenance_pg_host: Null
|
|
# evomaintenance_pg_passwd: Null
|
|
# evomaintenance_pg_db: Null
|
|
# evomaintenance_pg_table: Null
|
|
# evomaintenance_from_domain: "{{ evomaintenance_realm }}"
|
|
# evomaintenance_from: "evomaintenance@{{ evomaintenance_from_domain }}"
|
|
# evomaintenance_full_from: "Evomaintenance <{{ evomaintenance_from }}>"
|
|
# evomaintenance_urgency_from: mama.doe@example.com
|
|
# evomaintenance_urgency_tel: "06.00.00.00.00"
|
|
#
|
|
# evobsd_ssh_group: "foo-ssh"
|
|
# evobsd_sudo_group: "foo-sudo"
|
|
#
|
|
# evolix_users:
|
|
# foo:
|
|
# name: foo
|
|
# uid: 1042
|
|
# fullname: 'Foo Bar (Evolix)'
|
|
# groups: []
|
|
# password_hash_openbsd: ''
|
|
# ssh_keys:
|
|
# - 'ssh-rsa XXXXXXX'
|