There is no exact correspondence between the 'org.gnome.x.y' schemas for
gsettings and the DConf '/org/gnome/x/y' paths. In the particular case
of the 'org.gnome.system.proxy' schema, the corresponding DConf path is
in fact '/system/proxy' ...
Closes#10
Default SSSD template for ccache file is /tmp/krb5cc_%U_XXXXXX, where
XXXXXX is a suffix that will be interpreted by mkstemp(3) to create a
unique file name, while the standard configuration of the libkrb5
library is `/tmp/krb5cc_%U`.
To guarantee compatibility with the existing system, we force the use
of the standard model in SSSD.
Mark PAM profiles krb5, sss and yourdev as "seen" in /var/lib/pam so
next execution of command /usr/sbin/pam-auth-update in interactive
mode will ignore the values of 'Default' properties.
This avoids the automatic selection of the sss profile, which conflicts
with the yourdev profile.
Rationale: when configured with /etc/krb5.conf, SSSD ignores the values
of dns_lookup_kdc and dns_lookp_realm properties, ignores the static kdc
servers declared in the [realms] section, and always try to find the
Kerberos TGT servers using DNS _srv_ discovery, based on the realm name
as search domain (which is not optimal in the Orange network).
It's easier to define how to get the list of Kerberos servers from the
SSSD configuration, because then you can either give a static list of
servers or use DNS discovery by specifying the right search domain.
If krb5_use_kdcinfo property value is true (the default), then the
Kerberos servers are taken from sssd.conf, otherwise if the value is
false then the servers are taken from krb5.conf
Presence of comments in pam-configs/ file cause several warnings when
invoking command `pam-auth-updates` (use of uninitialized value), and
then later the PAM configuration is broken:
- SSH login fails immediately (connection closed)
- opening a session with `sudo su -` is impossible (authorisation refused)
- and maybe more...
Without comments in /usr/share/pam-configs/yourdev, everything works as
expected, no warnings in `pam-auth-updates`, no authentication problems.
