From 2b65809ad344770e185a9d45f7d89ff871c754a1 Mon Sep 17 00:00:00 2001 From: Michael Carbone Date: Thu, 20 Oct 2016 19:28:12 +0200 Subject: [PATCH] removed gendered language --- security/split-gpg.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/security/split-gpg.md b/security/split-gpg.md index 03bf6b51..719b1c35 100644 --- a/security/split-gpg.md +++ b/security/split-gpg.md @@ -258,9 +258,9 @@ In this example, the following keys are stored in the following locations leave the `vault` VM, so it is extremely unlikely ever to be obtained by an adversary (see below). Second, an adversary who *does* manage to obtain the master secret key either possesses the passphrase to unlock the key - (if one is used), or he does not. If he does, then he can simply use + (if one is used), or they do not. If they do, then they can simply use the passphrase in order to legally extend the expiration date of the key - (or remove it entirely). If he does not, then he cannot use the key at + (or remove it entirely). If they do not, then they cannot use the key at all. In either case, an expiration date provides no additional benefit. By the same token, however, having a passphrase on the key is of little