Skip Menu |

Subject: Bad KDC/kadmind error message when verto initialization fails
Date: Mon, 15 Jun 2020 13:02:42 -0400
From: describes a scenario where verto_default() fails, preventing the KDC or kadmind from starting.  We know that an external libverto was used, but aren't sure on any other details.

This scenario produces a misleading "Cannot allocate memory" message on both krb5kdc and kadmind.  loop_init() returns a verto context pointer or NULL, and the call sites assume that ENOMEM is the only possible cause of failure.