summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorRuss Allbery <rra@stanford.edu>2013-02-13 12:13:41 -0800
committerRuss Allbery <rra@stanford.edu>2013-02-13 12:42:11 -0800
commit3733b1537c987a42e4c3f6b30f4ccfef378e7cfc (patch)
treeb18612bc5190900810503d2f55a604bc95044050 /docs
parent4948053f7fd8a19f5c645d535ea3fa96f9539f4e (diff)
Add ssl-keypair to Stanford naming policy
Used currently by MDM to store both the certificate and the key in the same file for convenience. Change-Id: I38901ac93fe3022c2e00f735a0f995500841d709 Reviewed-on: https://gerrit.stanford.edu/784 Reviewed-by: Russ Allbery <rra@stanford.edu> Tested-by: Russ Allbery <rra@stanford.edu>
Diffstat (limited to 'docs')
-rw-r--r--docs/stanford-naming10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/stanford-naming b/docs/stanford-naming
index aa59f68..5207c40 100644
--- a/docs/stanford-naming
+++ b/docs/stanford-naming
@@ -141,6 +141,16 @@ Object Naming
(OLD: <group>-<server>-ssl-key)
+ ssl-keypair/<server>[/<application>]
+
+ Same as ssl-key except that the signed certificate is included in
+ the same file as the private key. This is used for convenience
+ with some applications that want to have both the signed
+ certificate and private key in the same file.
+
+ The meaning of <server> and <application> are the same as for
+ ssl-key.
+
tivoli-key/<server>
The Tivoli password or backup encryption key for this server.