Home | History | Annotate | Download | only in hdb

Lines Matching defs:kvno

76     16: kvno
408  * @param target_kvno	Desired kvno, or 0 for the entry's current kvno
409  * @param entry		Desired kvno, or 0 for the entry's current kvno
571      * 16: kvno
578      * keys for this kvno, the second meaning there's keys and salt[s?].
601 	if ((target_kvno == 0 && entry->kvno < key_kvno) ||
602 	    (target_kvno == key_kvno && entry->kvno != target_kvno)) {
604 	     * MIT's KDB doesn't keep track of kvno.  The highest kvno
605 	     * is the current kvno, and we just found a new highest
606 	     * kvno or the desired kvno.
610 	     * descending kvno order.
612 	     * XXX We do assume that keys are clustered by kvno.  If
628 	    entry->kvno = key_kvno;
632 	if (entry->kvno == key_kvno) {
635 	     * end up adding those keys here.  Yeah, kvno 0 is very
642 	    entry->kvno = key_kvno;
651     if (target_kvno != 0 && entry->kvno != target_kvno) {
944 	       unsigned flags, krb5_kvno kvno, hdb_entry_ex *entry)
956     ret = _hdb_mdb_value2entry(context, &value, kvno, &entry->entry);
1187   %d\t%d\t (key data version, kvno)
1453         int kvno;
1463         kvno = getint(&p, "kvno");
1464         CHECK_UINT16(kvno);
1465         ret = krb5_store_int16(sp, kvno);