Re: kdc-model-12 - enctypes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/06/2012 05:03 PM, Sam Hartman wrote:
>>>>>> "Zhanna" == Zhanna Tsitkov <[email protected]> writes:
> 
> Zhanna> Hi, Zhanna> In section 4.1.1.13 (principalAllowedEnctype)
> one reads: Zhanna> "If empty or absent any enctype supported by the
> implementation is Zhanna> allowed for this Principal". Zhanna> The
> problem here is that the "implementation" may have a wide range of 
> Zhanna> the enctypes, say, the flavors of des, aes, camellia. On
> the other Zhanna> hand, KDC might be configured to use only aes,
> meaning that neither Zhanna> des nor camellia would not be allowed
> for this Principal. right?
> 
> I certainly assume that's what is intended. One easy fi x would be
> to replace supported with permitted.

Sounds good.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/QXmEACgkQ8Jx8FtbMZnd4MwCgxLWMSfrmJr2aBupafxyTEb0a
NYsAn1Mp/uc8TiJ3FYorynXvCz2iZ+UG
=HbbZ
-----END PGP SIGNATURE-----
_______________________________________________
ietf-krb-wg mailing list
[email protected]
https://lists.anl.gov/mailman/listinfo/ietf-krb-wg