From 0b05924769ede3b99a4834fa7e86b5c27a2a443f Mon Sep 17 00:00:00 2001 From: Prashant D Date: Mon, 27 Sep 2021 13:37:31 +0100 Subject: [PATCH] doc/dev/cephx: fix typo Signed-off-by: Prashant D --- doc/dev/cephx.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/dev/cephx.rst b/doc/dev/cephx.rst index 27e501f9929..e060f7ec88e 100644 --- a/doc/dev/cephx.rst +++ b/doc/dev/cephx.rst @@ -10,7 +10,7 @@ Intro The protocol design looks a lot like kerberos. The authorizer "KDC" role is served by the monitor, who has a database of shared secrets for each entity. Clients and non-monitor daemons all start by -authenticating with the monitor to obtain tickets, mostly referreed to +authenticating with the monitor to obtain tickets, mostly referred to in the code as authorizers. These tickets provide both *authentication* and *authorization* in that they include a description of the *capabilities* for the entity, a concise structured @@ -402,5 +402,5 @@ That is, the new rotating key is simply protected by the daemon's rotating secret. Note that, as an implementation detail, the services keep the current -key and the prior key on hand so that the can continue to validate +key and the prior key on hand so that they can continue to validate requests while the key is being rotated.