Description of problem:
For the purposes of Fedora crypto-policies we generate configuration files for multiple applications/libraries. For the krb5 policy however the generated configuration file cannot be tested for correctness, other than by manually inspecting the file. That means that a CI testing infrastructure will not detect any bugs introduced to this generation.

Please provide some way to verify whether a generated configuration is valid, i.e., no typos are present, and the configuration provides at least one valid encryption option.