---
name: "verify_krb5_conf"
section: "8"
platform: "linux"
package: "heimdal-clients"
version: "7.8.git20221117.28daf24+dfsg-9+deb13u1"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/verify_krb5_conf"
---

# verify\_krb5\_conf(8)

checks krb5.conf for obvious errors

## NAME

**verify\_krb5\_conf** – checks krb5.conf for obvious errors

## SYNOPSIS

**verify\_krb5\_conf** *\[config-file\]*

## DESCRIPTION

**verify\_krb5\_conf** reads the configuration file *krb5.conf*, or the file given on the command line, parses it, checking verifying that the syntax is not correctly wrong.

If the file is syntactically correct, **verify\_krb5\_conf** tries to verify that the contents of the file is of relevant nature.

## ENVIRONMENT

KRB5\_CONFIG points to the configuration file to read.

## FILES

- */etc/krb5.conf*

  Kerberos 5 configuration file

## DIAGNOSTICS

Possible output from **verify\_krb5\_conf** include:

- \<path\>: failed to parse \<something\> as size/time/number/boolean

  Usually means that \<something\> is misspelled, or that it contains weird characters. The parsing done by **verify\_krb5\_conf** is more strict than the one performed by libkrb5, so strings that work in real life might be reported as bad.

- \<path\>: host not found (\<hostname\>)

  Means that \<path\> is supposed to point to a host, but it can't be recognised as one.

- \<path\>: unknown or wrong type

  Means that \<path\> is either a string when it should be a list, vice versa, or just that **verify\_krb5\_conf** is confused.

- \<path\>: unknown entry

  Means that \<string\> is not known by **verify\_krb5\_conf**.

## SEE ALSO

[krb5.conf(5)](/krb5.conf/5.md)

## BUGS

Since each application can put almost anything in the config file, it's hard to come up with a watertight verification process. Most of the default settings are sanity checked, but this does not mean that every problem is discovered, or that everything that is reported as a possible problem actually is one. This tool should thus be used with some care.

It should warn about obsolete data, or bad practice, but currently doesn't.