I didn't.
I have the server's public key on the client.
When I ssh'd from the client to the server, I only got the known_hosts and then terminated the
connection. In retrospect, I'm not sure I even needed that. I should try setting aside known_hosts
on the client and see if amcheck on the server still works. In any case, I never fully ssh in as
amanda or as backup. I don't even remember the password for amanda. I set it to something outrageous
and then promptly forgot it. I log in as myself and use sudo to get to amanda if needed.
For amrecover, I typically run it on the server and then move things to the
client, if needed.
On 4/14/17 3:27 PM, Charles Curley wrote:
On Fri, 14 Apr 2017 14:37:17 -0400
Chris Hoogendyk <hoogen...@bio.umass.edu> wrote:
I think that's it. Relatively simple once you get it. Hope I didn't
miss documenting any steps.
Looks good. I like locking down the keys to a specific executable.
I don't see where you generated the client's keys, or copied its public
key to the server. Those steps should be between steps 4 and 5 on the
client.
And if you want to run amrecover on the client, you will need to
copy user backup's public key from the client to the server.
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geosciences Departments
(*) \(*) -- 315 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<hoogen...@bio.umass.edu>
---------------
Erdös 4
