diff options
author | Russ Allbery <rra@stanford.edu> | 2006-12-08 22:06:06 +0000 |
---|---|---|
committer | Russ Allbery <rra@stanford.edu> | 2006-12-08 22:06:06 +0000 |
commit | e22a77c9fd62bc7f81c3edd2342f85cf4604f8e5 (patch) | |
tree | 261c1132a93a8c6c8ae9434b849aa8a0fd6044c1 /doc | |
parent | 415be76ff937b72bbc8f8c595d3ee7d5a2876b88 (diff) |
Need to use -clearpolicy with addprinc.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/notes | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -117,6 +117,11 @@ Server Issues doing the principal creation or randomization, separated by spaces and enclosed in double quotes. + When creating a new principal with addprinc, pass the -clearpolicy + flag. Otherwise, the principal will be placed in the default policy + and will be subject to password strength checking, and the initial + password used with -randkey will fail. + Whenever we generate a new keytab, we may need to push the key into K4. We could make the client send a flag saying whether they want synchronization with K4, but it's easier to just always do it (except |