Continue after KRB5_CC_END in KCM cache iteration The KCM server returns KRB5_CC_END in response to a GET_CACHE_BY_UUID request to indicate that the specified ccache uuid no longer exists. In krb5_ptcursor_next(), ignore this error and continue the iteration, as the Heimdal KCM client code does. In addition to addressing the case where a third party deletes a cache between the GET_CACHE_UUID_LIST request and when we reach that uuid in the iteration, this change also fixes a bug in kdestroy -A where the caller deletes the primary cache and we later request it by uuid when iterating over the list. [ghudson@mit.edu: rewrote commit message; edited comment] (cherry picked from commit 49087f5e6309f298f8898c35af6f4ade418ced60) https://github.com/krb5/krb5/commit/e5c2e8323f9b30a993ae7a1577f091fbbc7e7768 Author: Fabiano Fidêncio Committer: Greg Hudson Commit: e5c2e8323f9b30a993ae7a1577f091fbbc7e7768 Branch: krb5-1.15 src/lib/krb5/ccache/cc_kcm.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-)