URL: https://github.com/freeipa/freeipa/pull/738
Title: #738: restore: restart gssproxy after restore
frozencemetery commented:
"""
The systemd-portable way to do this is as I understand it is `systemctl
try-reload-or-restart gssproxy` (unless you want to start it if it
URL: https://github.com/freeipa/freeipa/pull/623
Title: #623: client install: do not assume /etc/krb5.conf.d exists
frozencemetery commented:
"""
(Note: a standard directory in distributions that freeipa could use would be
provided by the krb5 maintainer, not the freeipa mainta
URL: https://github.com/freeipa/freeipa/pull/410
Title: #410: ipa-kdb: support KDB DAL version 6.1
frozencemetery commented:
"""
@simo5 @abbra I'll move it over, but it won't break anything to pull in
krb5-devel *and* krb5-kdb-version as far as I can tell.
"""
URL: https://github.com/freeipa/freeipa/pull/410
Title: #410: ipa-kdb: support KDB DAL version 6.1
frozencemetery commented:
"""
@simo5 @abbra I'll move it over, but it won't break anything to pull in
krb5-devel *and* krb5-kdb-version as far as I can tell.
"""
URL: https://github.com/freeipa/freeipa/pull/410
Title: #410: ipa-kdb: support KDB DAL version 6.1
frozencemetery commented:
"""
There was talk of exporting a minor dal version but I think upstream explicitly
doesn't want it.
freeipa.spec.in should be modified if I under
URL: https://github.com/freeipa/freeipa/pull/289
Title: #289: Require python-gssapi >= 1.2.0
frozencemetery commented:
"""
We (the python-gssapi team) do not believe that is correct. This problem with
enum34 is fixed in the latest 1.1.z release (1.1.4).
We also do have CI
URL: https://github.com/freeipa/freeipa/pull/205
Title: #205: Support DAL version 5 and version 6
frozencemetery commented:
"""
Thank you for fixing this, and futureproofing the next version bump. Unless
freeipa has a policy against it, I would prefer the use of designated
in
