Difference between revisions of "Release 1.9"
From K5Wiki
(→Performance) |
(→Administrator experience) |
||
| Line 28: | Line 28: | ||
== Administrator experience == |
== Administrator experience == |
||
| − | * [[Projects/Trace_logging|Trace logging]] |
+ | * [[Projects/Trace_logging|Trace logging]][Greg Hudson] |
| − | * Plugins for password sync |
+ | * Plugins for password sync [Tom Yu] |
| − | * Plugins for password quality checks |
+ | * Plugins for password quality checks [Tom Yu] |
| − | * OTP (only old SAM SecurID planned for now) |
+ | * OTP (only old SAM SecurID planned for now) [Tom Yu] |
== Protocol evolution == |
== Protocol evolution == |
||
Revision as of 11:32, 18 May 2010
This is the preliminary proposed goal set for the krb5-1.9 release. Please provide comments on the krbdev list. This page organizes the goals by the "guiding principles" listed in the roadmap.
Contents
Timeline
This is only an approximate timeline.
- 2010-09-01 -- make release branch
- 2010-12-01 -- final release
Code quality
- Python-based test framework [Greg, done, could be extended to include multi=realm test cases]
- KDC refactoring [Tom Yu]
- DAL cleanup [Greg Hudson]
Developer experience
- NSS crypto back end? [Bob Lyea]
- plugin framework evolution [Tom Yu, Zhanna Tsitkova]
- Naming extensions back end for exposing constrained delegation chain [Luke, done, needs review]
Performance
- account lockout performance improvements [Greg Hudson, done]
End-user experience
Administrator experience
- Trace logging[Greg Hudson]
- Plugins for password sync [Tom Yu]
- Plugins for password quality checks [Tom Yu]
- OTP (only old SAM SecurID planned for now) [Tom Yu]
