Jose Manuel Barrueco writes, on CitEc-run
> Christian, could you send us the public ssh key for the user which sends
> the data from RAS to adnetec@iripa?
In a conversation that I had with JMBC yesterday we determined that
it must have been us deleting a key that made the import stop during
our German meeting.
But scouring the auth.log*, I could not see key access being denied
to RAS.
Just now, I found that we did take a copy of the .ssh in .ssh.old
before making the change we did. So JMBC and I we are smarter than
we give ourselves credit for. ;-)
The only key that I can find for RAS could be
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAq2bLsgE9NV73YQ2SIuvy49w3rrdt984EytZMf0C9/gylJmnEwxghbsBSLNkSEDCPP3x7PnrKaEptoD+cotNe4cHKkN+QmQPkviV0NIhD5kn14bpgyqLlC9sUNDnzbG1m0BCHVZZMSiExvouWyRH9B0njNfa8W1xJc/9Cw0RKPt0= zimm(a)fondue.econ.uconn.edu
I added that key back to adnetec@iripa:.ssh/authorized_keys
--
Cheers,
Thomas Krichel http://openlib.org/home/krichel
skype:thomaskrichel
Jose Manuel Barrueco writes
> Yes, that's the case...
Looks like this is August 2017
root@iripa ~ # ls -l /etc/ssh/ssh_host_rsa_key.pub
-rw-r--r-- 1 root root 392 Aug 8 2017 /etc/ssh/ssh_host_rsa_key.pub
That is an problem on the RAS side then? It should have been
discussed on the RAS mailing list.
And I should try to remember to copy keys when I install
a machine that is a successor to another machine.
It would be safest for the RAS side to add the -o
"StrictHostKeyChecking=no" flag to the copying of RAS data to CitEc.
But I'm confused how you know that the key on the RAS machine is
missing since you don't have access to that machine? Or am I
underestimating the extent of your magic powers?
--
Cheers,
Thomas Krichel http://openlib.org/home/krichel
skype:thomaskrichel
