mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2024-12-23 15:40:01 -06:00
b5fbbd1957
With system-wide crypto policy in use, arcfour-hmac encryption type might be removed from the list of permitted encryption types in the MIT Kerberos library. Applications aren't prevented to use the arcfour-hmac enctype if they operate on it directly. Since FreeIPA supported and default encryption types stored in LDAP, on the server side we don't directly use a set of permitted encryption types provided by the MIT Kerberos library. However, this set will be trimmed to disallow arcfour-hmac and other weaker types by default. While the arcfour-hmac key can be generated and retrieved, MIT Kerberos library will still not allow its use in Kerberos protocol if it is not on the list of permitted encryption types. We only need this workaround to allow setting up arcfour-hmac key for SMB services where arcfour-hmac key is used to validate communication between a domain member and its domain controller. Without this fix it will not be possible to request setting up a machine account credential from the domain member side. The latter is needed for Samba running on IPA client. Thus, extend filtering facilities in ipa-pwd-extop plugin to explicitly allow arcfour-hmac encryption type for SMB services (Kerberos principal name starts with cifs/). Reviewed-By: Christian Heimes <cheimes@redhat.com> |
||
|---|---|---|
| .. | ||
| 05-pre_upgrade_plugins.update | ||
| 10-config.update | ||
| 10-enable-betxn.update | ||
| 10-ipapwd.update | ||
| 10-rootdse.update | ||
| 10-selinuxusermap.update | ||
| 10-uniqueness.update | ||
| 19-managed-entries.update | ||
| 20-aci.update | ||
| 20-default_password_policy.update | ||
| 20-dna.update | ||
| 20-enable_dirsrv_plugins.update | ||
| 20-host_nis_groups.update | ||
| 20-idoverride_index.update | ||
| 20-indices.update | ||
| 20-ipaservers_hostgroup.update | ||
| 20-nss_ldap.update | ||
| 20-replication.update | ||
| 20-sslciphers.update | ||
| 20-syncrepl.update | ||
| 20-user_private_groups.update | ||
| 20-uuid.update | ||
| 20-whoami.update | ||
| 20-winsync_index.update | ||
| 21-ca_renewal_container.update | ||
| 21-certstore_container.update | ||
| 21-replicas_container.update | ||
| 25-referint.update | ||
| 30-ipservices.update | ||
| 30-provisioning.update | ||
| 30-s4u2proxy.update | ||
| 37-locations.update | ||
| 40-automember.update | ||
| 40-certprofile.update | ||
| 40-delegation.update | ||
| 40-dns.update | ||
| 40-otp.update | ||
| 40-realm_domains.update | ||
| 40-replication.update | ||
| 40-vault.update | ||
| 41-caacl.update | ||
| 41-lightweight-cas.update | ||
| 45-roles.update | ||
| 50-7_bit_check.update | ||
| 50-dogtag10-migration.update | ||
| 50-externalmembers.update | ||
| 50-groupuuid.update | ||
| 50-hbacservice.update | ||
| 50-ipaconfig.update | ||
| 50-krbenctypes.update | ||
| 50-nis.update | ||
| 55-pbacmemberof.update | ||
| 59-trusts-sysacount.update | ||
| 60-trusts.update | ||
| 61-trusts-s4u2proxy.update | ||
| 62-ranges.update | ||
| 71-idviews-sasl-mapping.update | ||
| 71-idviews.update | ||
| 72-domainlevels.update | ||
| 73-certmap.update | ||
| 73-custodia.update | ||
| 73-winsync.update | ||
| 80-schema_compat.update | ||
| 90-post_upgrade_plugins.update | ||
| Makefile.am | ||
| README | ||
The update files are sorted before being processed because there are cases where order matters (such as getting schema added first, creating parent entries, etc). Updates are applied in blocks of ten so that any entries that are dependant on another can be added successfully without having to rely on the length of the DN to get the sorting correct. The file names should use the format #-<description>.update where # conforms to this: 10 - 19: Configuration 20 - 29: 389-ds configuration, new indices 30 - 39: Structual elements of the DIT 40 - 49: Pre-loaded data 50 - 59: Cleanup existing data 60 - 69: AD Trust 70 - 79: Reserved 80 - 89: Reserved These numbers aren't absolute, there may be reasons to put an update into one place or another, but by adhereing to the scheme it will be easier to find existing updates and know where to put new ones.