XPost: uk.comp.os.linux   
   From: invalid@invalid.invalid   
      
   Java Jive  writes:   
   > As per subject, I have a number of Windows 7 PCs which are running an   
   > old-ish 32-bit version of ssh via CygWin and PuTTy.  Several of these   
   > machines dual-boot between Windows and Ubuntu22.  I also have a number   
   > of servers and network media players, 4 pretty old, 2 much newer.   
   >   
   > The machines running under Windows can log into the old servers via   
   > the old-ish 32-bit ssh and Cygwin using a public key file, no password   
   > is required, but to log into the newer servers, I have to use PuTTy.   
   >   
   > However, when booted into Ubuntu 22 none of the machines, even though   
   > they're using the *SAME* key files, can login in using just these   
   > public keys, a password is requested for both old and new servers.  I   
   > never had this problem with Ubuntu 18.   
   >   
   > I've checked all the usual suspects:   
   >   
   >   +  The id_rsa* copied into ~/.ssh are identical to those used by the   
   >   Windows builds.   
      
   What size is the key? To find out:   
     ssh-keygen -l -f .ssh/id_rsa.pub   
      
   > ... results in the output appended.  Can anyone help explain what is   
   > going wrong and help fix the problem?  My first suspicion is that a   
   > newer version of ssh in the Ubuntu 22 builds is not accepting the   
   > older keys accepted by Ubuntu 18, so, if this is true,   
      
   That is quite likely.   
      
   > Debug output:   
      
   > debug1: Will attempt key: /user/.ssh/id_rsa.pub RSA SHA256: key, not the one in id_rsa or id_rsa.pub> explicit   
      
   How are you determining that it’s not the same key? My guess is that   
   you’ve tried to compare the SHA256 hash to the public key material. You   
   need to compare hashes with hashes, or public keys with public keys.   
      
   > debug1: Offering public key: /user/.ssh/id_rsa.pub RSA SHA256: unknown key, not the one in id_rsa or id_rsa.pub> explicit   
   > debug1: send_pubkey_test: no mutual signature algorithm   
      
   The server did not accept your key.   
      
   > However, the same key file   
      
   Your message seems to be truncated.   
      
      
   There’s not enough information here to be sure (server debug output   
   might help) but my guess is that you’re trying to use an RSA-1024 key   
   with a modern SSH server, which rejects it as too weak. If you are still   
   using RSA-1024 then it’s time for new keys.   
      
   --   
   https://www.greenend.org.uk/rjk/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)