From krichel at openlib.org  Thu Jan  9 09:46:16 2020
From: krichel at openlib.org (Thomas Krichel)
Date: Thu, 9 Jan 2020 09:46:16 +0000
Subject: [RAS] RAS -> CitEc
In-Reply-To: <alpine.WNT.2.20.2001091030000.5980@DESKTOP-HAQ8ITT>
References: <20191121180900.GB31958@openlib.org> <1364514945barrueco@uv.es>
 <20191121182039.GD31958@openlib.org>
 <alpine.WNT.2.20.2001090910310.5980@DESKTOP-HAQ8ITT>
 <20200109091147.GA8203@openlib.org>
 <alpine.WNT.2.20.2001091021050.5980@DESKTOP-HAQ8ITT>
 <20200109092828.GB8203@openlib.org>
 <alpine.WNT.2.20.2001091030000.5980@DESKTOP-HAQ8ITT>
Message-ID: <20200109094616.GC8203@openlib.org>

  Jose Manuel Barrueco writes

> Yes, that's the case...

  Looks like this is August 2017

root at 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


From zimmermann at stlouisfed.org  Thu Jan  9 16:28:57 2020
From: zimmermann at stlouisfed.org (Christian Zimmermann)
Date: Thu, 9 Jan 2020 16:28:57 +0000
Subject: [RAS] [External]  Re:  RAS -> CitEc
In-Reply-To: <20200109094616.GC8203@openlib.org>
References: <20191121180900.GB31958@openlib.org> <1364514945barrueco@uv.es>
 <20191121182039.GD31958@openlib.org>
 <alpine.WNT.2.20.2001090910310.5980@DESKTOP-HAQ8ITT>
 <20200109091147.GA8203@openlib.org>
 <alpine.WNT.2.20.2001091021050.5980@DESKTOP-HAQ8ITT>
 <20200109092828.GB8203@openlib.org>
 <alpine.WNT.2.20.2001091030000.5980@DESKTOP-HAQ8ITT>
 <20200109094616.GC8203@openlib.org>
Message-ID: <0100016f8b233122-e073c597-cb6f-473d-b9f9-ca8bc8c83c77-000000@email.amazonses.com>

So what do we need to do in St. Louis?

Christian Zimmermann                          FIGUGEGL!
Economic Research
Federal Reserve Bank of St. Louis
P.O. Box 442
St. Louis MO 63166-0442 USA
https://ideas.repec.org/zimm/   @CZimm_economist

On Thu, 9 Jan 2020, Thomas Krichel wrote:

>  Jose Manuel Barrueco writes
>
>> Yes, that's the case...
>
>  Looks like this is August 2017
>
> root at 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
>
> _______________________________________________
> RAS-run mailing list
> RAS-run at lists.openlib.org
> http://lists.openlib.org/cgi-bin/mailman/listinfo/ras-run
>


From krichel at openlib.org  Tue Jan 14 08:57:16 2020
From: krichel at openlib.org (Thomas Krichel)
Date: Tue, 14 Jan 2020 08:57:16 +0000
Subject: [RAS] RAS -> CitEc
In-Reply-To: <alpine.WNT.2.20.2001140913130.6860@DESKTOP-HAQ8ITT>
References: <20191121175147.GA16130@openlib.org> <7846266891barrueco@uv.es>
 <0100016e8f427003-9ec37074-3ff4-42e3-9ad7-751891f303e9-000000@email.amazonses.com>
 <alpine.WNT.2.20.2001140913130.6860@DESKTOP-HAQ8ITT>
Message-ID: <20200114085716.GC11347@openlib.org>

  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 at 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 at fondue.econ.uconn.edu

  I added that key back to adnetec at iripa:.ssh/authorized_keys


-- 

  Cheers,

  Thomas Krichel                  http://openlib.org/home/krichel
                                              skype:thomaskrichel


