mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2024-12-25 08:21:05 -06:00
3cf9979aec
sshd 8.2+ now supports the "Include" keyword in sshd_config and ships by default /etc/ssh/sshd_config with "Include /etc/ssh/sshd_config.d/*" As fedora 32 provides a config file in that directory (05-redhat.conf) with ChallengeResponseAuthentication no that is conflicting with IPA client config, ipa-client-install now needs to make its config changes in a drop-in file read before 05-redhat.conf (the files are read in lexicographic order and the first setting wins). There is no need to handle upgrades from sshd < 8.2: if openssh-server detects a customisation in /etc/ssh/sshd_config, it will not update the file but create /etc/ssh/sshd_config.rpmnew and ask the admin to manually handle the config upgrade. Fixes: https://pagure.io/freeipa/issue/8304 Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com> |
||
|---|---|---|
| .. | ||
| certmonger | ||
| custodia | ||
| html | ||
| migration | ||
| oddjob | ||
| restart_scripts | ||
| share | ||
| tools | ||
| ui | ||
| updates | ||
| wsgi | ||
| Makefile.am | ||
| README.schema | ||
Ground rules on adding new schema Brand new schema, particularly when written specifically for IPA, should be added in share/*.ldif. Any new files need to be explicitly loaded in ipaserver/install/dsinstance.py. These simply get copied directly into the new instance schema directory. Existing schema (e.g. in an LDAP draft) may either be added as a separate ldif in share or as an update in the updates directory. The advantage of adding the schema as an update is if 389-ds ever adds the schema then the installation won't fail due to existing schema failing to load during bootstrap. If the new schema requires a new container then this should be added to install/bootstrap-template.ldif.