From: robin_listas@es.invalid   
      
   On 2017-08-02 08:08, Werner Flamme wrote:   
   > Paulo da Silva [02.08.2017 03:32]:   
   >> Às 02:02 de 02-08-2017, Carlos E.R. escreveu:   
   >>> On 2017-08-02 00:39, Paulo da Silva wrote:   
   >> ...   
   >>   
   >>>> Should I respond yes here?   
   >>>   
   >>> If you want to install chrome, yes, of course.   
   >> Isn't this a insecure procedure?   
   >   
   > Yes, it is.   
   >   
   >>   
   >>>   
   >>>> Any other fix?   
   >>>   
   >>> Yes. You can Fax Google and ask them to send by certified mail their new   
   >>> key. Then compare the new key you receive with the one on the repo, and   
   >>> if it is the same, accept.   
   >> I was thinking of somehow getting the new key and replacing it.   
   >>   
   >   
   > That requires Google to publish it and to maintain the repodata   
   > correctly. At least the latter obviously causes problems now ;)   
      
   Thus the irony of my response... ;-)   
      
   > Trying to look at the repo's contents tells me only "404. That’s an   
   > error. That’s all we know." So the repo may be hijacked or whatever.   
      
   Using YaST, it automatically asks to update the key. If you want the   
   update, you have to do it.   
      
   --   
   Cheers,   
          Carlos E.R.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)