This launchpad bug was "overloaded" and is talking about 3 issues:
a) kinit fails for OTP user when using kdc discovery via DNS - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 - debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307 - debian patch: 0013-Fix-udp_preference_limit-with-SRV-records.patch
b) KDC/kadmind explicit wildcard listener addresses do not use pktinfo - no LP bug - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530 - debian: conflated into https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767 - debian patch: 0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch
c) KDC/kadmind may fail to start on IPv4-only systems - no LP bug - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531 - debian: also conflated into https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767 - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch
I'll file separate bugs for (b) and (c) including test cases and then the SRU can address them too. I'm now working on a test case for (a).
This launchpad bug was "overloaded" and is talking about 3 issues:
a) kinit fails for OTP user when using kdc discovery via DNS krbdev. mit.edu/ rt/Ticket/ Display. html?id= 8554 bugs.debian. org/cgi- bin/bugreport. cgi?bug= 856307 udp_preference_ limit-with- SRV-records. patch
- upstream: http://
- debian: http://
- debian patch: 0013-Fix-
b) KDC/kadmind explicit wildcard listener addresses do not use pktinfo krbdev. mit.edu/ rt/Ticket/ Display. html?id= 8530 /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 860767 pktinfo- for-explicit- UDP-wildcard- listeners. patch
- no LP bug
- upstream: http://
- debian: conflated into https:/
- debian patch: 0012-Use-
c) KDC/kadmind may fail to start on IPv4-only systems krbdev. mit.edu/ rt/Ticket/ Display. html?id= 8531 /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 860767 KDC-kadmind- startup- on-some- IPv4-only- systems. patch
- no LP bug
- upstream: http://
- debian: also conflated into https:/
- debian patch: 0011-Fix-
I'll file separate bugs for (b) and (c) including test cases and then the SRU can address them too. I'm now working on a test case for (a).