Re: ssh issue that I don't understand

On lun., 2026-07-06 at 15:25 +0500, Alexander V. Makartsev wrote:
>  
> On 7/6/26 12:50, Chris Green wrote:
>  
>  
> >  
> > Alexander V. Makartsev <[email protected]> wrote:
> >  
> > >  
> > > [-- text/plain, size 1.3K, charset UTF-8, 43 lines, encoding 8bit
> > > --]
> > > 
> > > On 7/6/26 00:19, Chris Green wrote:
> > >  
> > > >  
> > > > ...
> > > > 'host isbd.biz' returns the correct IP address for isbd.biz so
> > > > why
> > > > does ssh not work using the name rather than the IP address?
> > > > 
> > > >  
> > >  
> > > Check your ssh client config file (should be at
> > > /home/chris/.ssh/config)
> > > You probably didn't setup it for the host isbd.biz, or didn't put
> > > the 
> > > IdentityFile directive correctly.
> > > The host entry in your case should look like this:
> > > 
> > > Host isbd.biz
> > >    HostName isbd.biz
> > >    Port 22
> > >    User chris
> > >    IdentityFile ~/.ssh/my-ssh-key-for-isbd-biz.key
> > > 
> > >  
> >  
> > But that's all default settings. Sites work without entries in
> > ~/.ssh/config if the configuration is as you've shown above.
> > 
> >  
>  SSH client uses password authentication by default, so if you want
> to authenticate with private key then you need to explicitly setup
> "IdentityFile" directive or use "-i" command line parameter to select
> a key file.
>  It is a good practice, at least for me, to explicitly setup separate
> entries for each host, because different hosts might have different
> keys, different ports and protocols, different users, different
> encryption algorithms, etc.
>  If you have one-ssh-key-for-everything and always use the default
> port, then you can use "Host *" directive to choose default settings,
> but doing this might complicate things in the future.
> 
Port xxxx
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes

you need to

ssh-copy-id -i ~/.ssh/keyname user@host

sudo systemctl restart sshd

regards,
jean-christophe