summaryrefslogtreecommitdiff
path: root/docs/stanford-naming
AgeCommit message (Collapse)Author
2013-02-27Add license statements to all textual documentation in docsRuss Allbery
Change-Id: Id5af9714e3d4f516cf7391c869eff89521e145c5 Reviewed-on: https://gerrit.stanford.edu/849 Reviewed-by: Russ Allbery <rra@stanford.edu> Tested-by: Russ Allbery <rra@stanford.edu>
2013-02-13Add ssl-keypair to Stanford naming policyRuss Allbery
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>
2013-02-05Add another case to the Stanford ssl-key naming conventionRuss Allbery
If there are multiple SSL private keys for the same host-based CN, an application name can be added as an additional component of the name. Change-Id: I06e25359b291a77a7dbca1a7f3db84afb2b16ddd Reviewed-on: https://gerrit.stanford.edu/754 Reviewed-by: Russ Allbery <rra@stanford.edu> Tested-by: Russ Allbery <rra@stanford.edu>
2013-01-18Further Stanford naming convention changesRuss Allbery
Remove the group for host-based file object names. Move the group to the second component for non-host-based names so that the first component is always the object type. Add some additional object types and clarify wording based on feedback from Adam. Change-Id: I5db7b23d2b004c69afb869df5624d455b751c0d5 Reviewed-on: https://gerrit.stanford.edu/724 Reviewed-by: Russ Allbery <rra@stanford.edu> Tested-by: Russ Allbery <rra@stanford.edu>
2013-01-17Significant revision of the Stanford naming schemeRuss Allbery
Recommend slash-separated names by default. Remove some obsolete bits and update a lot of the recommendations and wording. Change-Id: I44cbf8116e7529b00a61261248ff9daecacdb910 Reviewed-on: https://gerrit.stanford.edu/723 Reviewed-by: Russ Allbery <rra@stanford.edu> Tested-by: Russ Allbery <rra@stanford.edu>
2011-03-23Add -ssl-keystore to the Stanford naming conventionsRuss Allbery
2010-04-14Update Stanford naming for Tivoli keysRuss Allbery
The previous wording implied that <group>-<server>-tivoli-key was only used for encryption keys. Allow for either passwords or encryption keys, and remove the note that it should be base64-encoded since wallet now supports binary files.
2010-01-13Add Tivoli encryption keys to the Stanford naming guideRuss Allbery
2009-08-15Add a naming convention for general config filesRuss Allbery
We have some general configuration files that contain database passwords. Add a general naming convention to avoid creating new ones with each new type of config file.
2009-08-07Update Stanford naming documentation for puppet.confRuss Allbery
Add a naming convention for puppet.conf files containing secure data and reorganize the naming convention documentation to group all service objects together.
2009-03-25Add the shibboleth.xml object naming convention.Russ Allbery
2009-02-27Add htpasswd convention.Russ Allbery
2008-12-15Add ssh key naming to the Stanford naming guide.Russ Allbery
2008-10-06Add additional Stanford naming conventions.Russ Allbery
2008-09-17Clarify database password object naming and add PAM configuration objectRuss Allbery
naming.
2008-07-07Initial Stanford naming conventions.Russ Allbery