From 5863adf994b6491567971d2699449daad04e7f8e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Mon, 9 Nov 2020 17:01:57 -0500
Subject: [PATCH] word wrap
---
policy/tpa-rfc-7-root.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/policy/tpa-rfc-7-root.md b/policy/tpa-rfc-7-root.md
index a7e1494e..9e3100e3 100644
--- a/policy/tpa-rfc-7-root.md
+++ b/policy/tpa-rfc-7-root.md
@@ -18,9 +18,10 @@ There are multiple possible access levels, often conflated:
their SSH keys authorized to the root user (through Puppet, in the
`profile::admins::keys` Hiera field)
2. `sudo` to root: user has access to the `root` user through `sudo`,
- using their `sudoPassword` defined in LDAP3. Puppet access: by virtue of being able to push to the Puppet git
- repository, an admin necessarily gets `root` access everywhere,
- because Puppet runs as root everywhere
+ using their `sudoPassword` defined in LDAP3. Puppet access: by
+ virtue of being able to push to the Puppet git repository, an
+ admin necessarily gets `root` access everywhere, because Puppet
+ runs as root everywhere
4. LDAP admin: a user member of the `adm` group in LDAP also gets
access everywhere through `sudo`, but also through being able to
impersonate or modify other users in LDAP
--
GitLab