Hi Wim, this seems like a real quality bug report to me - thank you for that. I checked other versions up to the latest but eventually found that even in latest upstream the same code exists [1].
To fully understand that and also to make the change that eventually helps all downstreams and not only Ubuntu it would be best to file an issue there. In any case that should get the subject matter experts thoughts on it, and we can follow depending on what comes up in this upstream discussion. Please can you verify this by building directly from the latest upstream source? If this can be confirmed as an upstream bug, the best route to getting it fixed in Ubuntu in this case would be to file an upstream bug if you're able to do that. Otherwise, I'm not sure what we can do directly in Ubuntu to fix the problem. You could IMHO as well try the same on Ubuntu Bionic or Cosmis whihc has version 1.16 matching the latest upstream releases (well not the 1.6.1 release, but 1.6 at least). I'd highly appreciate if you file a bug upstream to mention it here to we can link up the bug tracking with it. [1]: https://github.com/krb5/krb5/blob/master/src/lib/krb5/asn.1/asn1_k_encode.c#L1128 ** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793594 Title: IAKERB-HEADER "Realm" field incorrectly encoded as OCTET STRING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1793594/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
