From 3a3c53327a44cb875becc070c79f0e14be19f56c Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Mon, 28 Nov 2005 07:59:46 +0000 Subject: r11940: Love has clarified why this code does what it does. Andrew Bartlett (This used to be commit 9b3dedbc0bb12897a8f9bd4ec864de26b3835981) --- source4/auth/kerberos/kerberos-notes.txt | 8 -------- 1 file changed, 8 deletions(-) (limited to 'source4/auth') diff --git a/source4/auth/kerberos/kerberos-notes.txt b/source4/auth/kerberos/kerberos-notes.txt index 25524ebba7..58a4159a7e 100644 --- a/source4/auth/kerberos/kerberos-notes.txt +++ b/source4/auth/kerberos/kerberos-notes.txt @@ -179,14 +179,6 @@ Other odd things: allow multiple passwords per account in krb5. (I think this was intened to allow multiple salts) - - When sending the enc-type negotiation, we call get_pa_etype_info if - there are only 'old' enc types present, but always call - get_pa_etype_info2. It would seem more logical to have an - either/or, or only send both to clients that show signs of knowing - about the old enc types. - - Perhaps this is to cope with clients that expect the older info in - the first position? (Comments needed) - State Machine safety -------------------- -- cgit