On Tue Mar 18 10:51:38 2025 +0000, Dmitry Timoshkov wrote:
According to KRB5_TRACE if password is NULL libkrb5 uses cached ticket for the specified user@domain, so, to me it looks like an intended behaviour.
Suppose a handle is acquired for user@domain with non-null password, then if you acquire another handle for user2@domain with null password you get cached credentials for user@domain.