Security guidelines Ssh access should be strongly limited.
(cherry picked from commit 63e3296b02bcef51e1cafa1471b690daee98c5e9) Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/29f15f9e Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/29f15f9e Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/29f15f9e Branch: refs/heads/0.11.x Commit: 29f15f9ee83186765abc7bee5c54362385c78dab Parents: ddfd9d2 Author: Valentin Aitken <[email protected]> Authored: Wed Apr 26 20:35:06 2017 +0300 Committer: Richard Downer <[email protected]> Committed: Wed May 31 15:26:23 2017 +0100 ---------------------------------------------------------------------- guide/ops/security-guidelines.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/29f15f9e/guide/ops/security-guidelines.md ---------------------------------------------------------------------- diff --git a/guide/ops/security-guidelines.md b/guide/ops/security-guidelines.md index b6e4460..3b86a23 100644 --- a/guide/ops/security-guidelines.md +++ b/guide/ops/security-guidelines.md @@ -72,7 +72,8 @@ root login. ### VM Users It is strongly discouraged to use the root user on VMs being created or managed by Brooklyn. - +SSH-ing on the VM should be done on rare cases such as initial Apache Brooklyn setup, +Apache Brooklyn upgrade and other important maintenance occasions. ### SSH keys
