From 50c62d7a4ba5321d38902f4d7e978ccf67ce57b6 Mon Sep 17 00:00:00 2001 From: patvdv Date: Sat, 3 Oct 2015 20:08:37 +0200 Subject: [PATCH] Update doc --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d22f01c..3b63a90 100644 --- a/README.md +++ b/README.md @@ -9,9 +9,9 @@ SUDO Controls is a light-weight **SUDO fragments/rules** distribution & manageme * uses a **two-stage** approach to activate **SUDO fragments**: copy (or distribute) and apply. Fragments are first copied into a temporary location on each client hosts - the holding directory - and not applied automatically. Applying or activating fragments on a client host is a separate operation which can be triggered either locally or remotely (from the SUDO master) -* allows the use of (nested) **groups** in the master configuration: users, fragments and hosts can be grouped in the SUDO master configuration files to allow a simplified configuration. Nesting of groups is allowed up to one level deep. +* allows the use of (nested) **groups** in the master configuration: fragments and hosts can be grouped in the SUDO master configuration files to allow a simplified configuration. Nesting of groups is allowed up to one level deep. -* can discover host public keys to (re)create `known_hosts` file(s) for a large amount of hosts +* can discover SSH host public keys to (re)create `known_hosts` file(s) for a large amount of hosts * requires **no client agent** component and is **stateless**: SUDO Controls performs operations by pushing fragments or commands to client hosts. Update processes on the client hosts will only be started on-demand. If the SUDO master is - for whatever reason - unavailable then active fragments on a client host remain in place.