From 801ac52ae0fe4be2b31c8043778e47e6f3c215f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Fri, 11 Oct 2019 12:35:44 -0400
Subject: [PATCH] double-check ssh
---
tsa/howto/postgresql.mdwn | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/tsa/howto/postgresql.mdwn b/tsa/howto/postgresql.mdwn
index 9461f81d..a349b8aa 100644
--- a/tsa/howto/postgresql.mdwn
+++ b/tsa/howto/postgresql.mdwn
@@ -127,7 +127,7 @@ server to the database server and restores from those.
3. And on the client, allow the server `$HOSTKEY` (the above `cat
/etc/ssh/ssh_host_rsa_key.pub` on the backup server):
- echo "$HOSTKEY" >> /etc/ssh/userkeys/root
+ echo "$HOSTKEY" >> /etc/ssh/userkeys/root.more
4. Then, we can transfer files over from the backup server to the
client:
@@ -183,6 +183,8 @@ server to the database server and restores from those.
11. re-enable Puppet, which should clean up the extra SSH key:
puppet agent -t
+
+ make sure it's okay in `/etc/ssh/userkeys/root`
When the restore succeeds, the `recovery.conf` file will be renamed to
`recovery.done` and you will see something like:
--
GitLab