| commit | c5d0acb8598bf6c4993458cb149341bbc0622705 | |
| author | Derrick Brashear <shadow@dementia.org> | |
| Mon, 6 Dec 2010 14:47:42 +0000 (6 09:47 -0500) | ||
| committer | Love Hornquist Astrand <lha@h5l.org> | |
| Fri, 25 Feb 2011 03:22:25 +0000 (24 19:22 -0800) | ||
| tree | 136bbabf2e8dfc322977407c6bcfec1c06bcdbec | treesnapshot (tar.gz zip) |
| parent | a7b851fad0d64cd29e2e39dd56c0ddc0a6312296 | commitdiff |
Correct "not newer" etypes per RFC 4121
Section 1 of RFC 4121 describes behavior which
applies when using "newer" etypes, then goes on in
table form to list etypes which are not newer.
While it specifies it is ok to use new token formats
when both initiator and acceptor are known to handle them,
this code makes no such verification, and encoded an
incorrect set of etypes as "not newer". Correct the list.
Signed-off-by: Love Hornquist Astrand <lha@h5l.org>
Section 1 of RFC 4121 describes behavior which
applies when using "newer" etypes, then goes on in
table form to list etypes which are not newer.
While it specifies it is ok to use new token formats
when both initiator and acceptor are known to handle them,
this code makes no such verification, and encoded an
incorrect set of etypes as "not newer". Correct the list.
Signed-off-by: Love Hornquist Astrand <lha@h5l.org>
| lib/gssapi/krb5/accept_sec_context.c | diffblobblamehistory |