| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Policy extensions + new policy: allowed ks types | Nicolas Williams | 2012-07-30 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | This simply adds KADM5_API_VERSION_4 and various fields to the policy structures: - attributes (policy-ish principal attributes) - max_life (max ticket life) - max_renewable_life (max ticket renewable life) - allowed_keysalts (allowed key/salt types) - TL data (future policy extensions) Of these only allowed_keysalts is currently implemented. Some refactoring of TL data handling is also done. ticket: 7223 (new) | ||||
| * | Try all history keys to decrypt password history | Greg Hudson | 2012-04-24 | 1 | -0/+99 |
| A database created prior to 1.3 will have multiple password history keys, and kadmin prior to 1.8 won't necessarily choose the first one. So if there are multiple keys, we have to try them all. If none of the keys can decrypt a password history entry, don't fail the password change operation; it's not worth it without positive evidence of password reuse. ticket: 7099 git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@25819 dc483132-0cff-0310-8789-dd5450dbe970 | |||||
 |
index : krb5.git | |
| Unnamed repository; edit this file 'description' to name the repository. | Günther Deschner |
| summaryrefslogtreecommitdiffstats |