On Thu, Jun 12, 2014 at 06:45:39PM +0200, Bastian Blank wrote: > On Wed, Jun 11, 2014 at 10:24:51PM +0200, Jelmer Vernooij wrote: > > On Wed, Jun 11, 2014 at 09:50:51PM +0200, Bastian Blank wrote: > > > kadmin is _not_ compatible, neither in the command-line interface nor in > > > the protocol. > > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=213316 for the > > discussion leading up to this change. > This is #482528, not #213316. It asks for co-installability of kadmin, > as this tool is specific to a particular implementation. It is not > needed, or better dangerous, for anything else. This does make them coinstallable, and both runnable (kadmin.heimdal and kadmin.mit).
> > These binaries do provide similar functionality, even if their > > interface isn't compatible. > > Please show me that you can connect with a heimdal kadmin to a MIT > kadmind. This kind of compatible is needed. Why is network-level compatibility the bar for "similar functionality" ? > > What is the justification for severity > > serious? > > Now it provides the same name for different CLI interfaces, which other > packages already use. Did you check each and every reverse-dependency > of krb5-user if it still works with the different interface that heimdal > provides? Yes, I could not find any existing callers for Heimdal's kadmin. krb5-user is not using alternatives yet. If there is something that requires the MIT kadmin specifically, it can call out to kadmin.mit. These tools are not just used by scripts. There are lots of alternatives on a Debian system that don't have the exact same user interface. Cheers, Jelmer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
