Hello tech,

some time ago we've introduced a K_AUTH table lookup method, to offload
the authentication handling to a proc table.  This is different from the
previous credentials tables because they are supposed to return the hash
of a password for the given user.

The only problem with this is that we have a lowercase() before reaching
the table itself, so for K_AUTH we end up lowercasing both the username
and the password.

The cautious reader will realize that this will leave also the username
with the original casing.  I'm a bit unsure about what to do.  For
K_AUTH the caller code will construct a string "username:password"
without changing the casing, then calls table_lookup().  Being pedantic,
the username *could* be case-sensitive, so there's a small argument for
keeping the case as-is.

okay?

diff /home/op/w/smtpd
path + /home/op/w/smtpd
commit - 56d54b2a7cc014527ea8ba0e2bacd270917079ed
blob - aca013debeab51e319144b92b5ac154bb6dca1ec
file + table.c
--- table.c
+++ table.c
@@ -144,7 +144,7 @@ table_lookup(struct table *table, enum table_service k
 	r = -1;
 	if (table->t_backend->lookup == NULL)
 		errno = ENOTSUP;
-	else if (!lowercase(lkey, key, sizeof lkey)) {
+	else if (kind != K_AUTH && !lowercase(lkey, key, sizeof lkey)) {
 		log_warnx("warn: lookup key too long: %s", key);
 		errno = EINVAL;
 	}