Ssh_config: Connection refused

Résolu
niconovice -  
Bonjour,

j'arrive pas comprendre pourquoi ?

mon fichier ssh_config est complètement commenté de base, est ce normal ?

# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

Host *
# ForwardAgent no
# ForwardX11 no
# ForwardX11Trusted yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# GSSAPIKeyExchange no
# GSSAPITrustDNS no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
SendEnv LANG LC_*
HashKnownHosts yes
GSSAPIAuthentication yes
GSSAPIDelegateCredentials no

Merci



--
Si tu cherches un bon casse tête, mets toi à l'informatique !

3 réponses

  1. axel55
    Logiquement c'est pour faciliter les modifications du fichier. Si par exemple vous voulez que le serveur écoute au port 344, vous remplacez 
    # Port 22
    par 
    Port 344
    et enlever donc le # pour que la modification soit effectif.
    0
    1. niconovice Auteur
      titre: Ssh_config: Connection refused

      je n'arrive pas à me connecter !!! et ma question est ce à cause du fichier ? si oui quel commentaire dois je enlever, etc...

      mais merci d'avoir essayé
      0
      1. zipe31 Contributeur
        Salut,

        Le serveur tourne-t-il au moins ?
        Quelle commande tapes-tu exactement ?
        C'est sur un réseau local ?
        1
        1. niconovice Auteur
          salut zipe31,

          le serveur tourne oui et j'essaye de me co depuis mon iphone...-.-

          iphone de nico:~mobiles$ ssh -v nico@192.168.1.12
          debug1: Reading configuration data /etc/ssh/ssh_config
          debug1: /etc/ssh/ssh_config line 19: Applying options for *
          debug1: Connecting to 192.168.1.12 [192.168.1.12] port 22.
          debug1: connect to address 192.168.1.12 port 22: Connection refused
          ssh: connect to host 192.168.1.12 port 22: Connection refused

          Ps: je suis en local (même wifi)
          0
        2. zipe31 Contributeur
          Bon à quoi ressemble le fichier sshd_config sur 192.168.1.12 ?
          0
        3. niconovice Auteur
          à ça:
          # Package generated configuration file
          # See the sshd_config(5) manpage for details

          # What ports, IPs and protocols we listen for
          Port 22
          # Use these options to restrict which interfaces/protocols sshd will bind to
          #ListenAddress ::
          #ListenAddress 0.0.0.0
          Protocol 2
          # HostKeys for protocol version 2
          HostKey /etc/ssh/ssh_host_rsa_key
          HostKey /etc/ssh/ssh_host_dsa_key
          HostKey /etc/ssh/ssh_host_ecdsa_key
          #Privilege Separation is turned on for security
          UsePrivilegeSeparation yes

          # Lifetime and size of ephemeral version 1 server key
          KeyRegenerationInterval 3600
          ServerKeyBits 768

          # Logging
          SyslogFacility AUTH
          LogLevel INFO

          # Authentication:
          LoginGraceTime 120
          PermitRootLogin yes
          StrictModes yes

          RSAAuthentication yes
          PubkeyAuthentication yes
          #AuthorizedKeysFile %h/.ssh/authorized_keys

          # Don't read the user's ~/.rhosts and ~/.shosts files
          IgnoreRhosts yes
          # For this to work you will also need host keys in /etc/ssh_known_hosts
          RhostsRSAAuthentication no
          # similar for protocol version 2
          HostbasedAuthentication no
          # Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
          #IgnoreUserKnownHosts yes

          # To enable empty passwords, change to yes (NOT RECOMMENDED)
          PermitEmptyPasswords no

          # Change to yes to enable challenge-response passwords (beware issues with
          # some PAM modules and threads)
          ChallengeResponseAuthentication no

          # Change to no to disable tunnelled clear text passwords
          #PasswordAuthentication yes

          # Kerberos options
          #KerberosAuthentication no
          #KerberosGetAFSToken no
          #KerberosOrLocalPasswd yes
          #KerberosTicketCleanup yes

          # GSSAPI options
          #GSSAPIAuthentication no
          #GSSAPICleanupCredentials yes

          X11Forwarding yes
          X11DisplayOffset 10
          PrintMotd no
          PrintLastLog yes
          TCPKeepAlive yes
          #UseLogin no

          #MaxStartups 10:30:60
          #Banner /etc/issue.net

          # Allow client to pass locale environment variables
          AcceptEnv LANG LC_*

          Subsystem sftp /usr/lib/openssh/sftp-server

          # Set this to 'yes' to enable PAM authentication, account processing,
          # and session processing. If this is enabled, PAM authentication will
          # be allowed through the ChallengeResponseAuthentication and
          # PasswordAuthentication. Depending on your PAM configuration,
          # PAM authentication via ChallengeResponseAuthentication may bypass
          # the setting of "PermitRootLogin without-password".
          # If you just want the PAM account and session checks to run without
          # PAM authentication, then enable this but set PasswordAuthentication
          # and ChallengeResponseAuthentication to 'no'.
          UsePAM yes
          0
        4. zipe31 Contributeur
          T'es sûr que ton serveur tourne ? (/etc/init.d/ssh status)

          Ton Iphone est bien sur le même réseau (192.168.1.xxx)

          Est-ce que depuis 192.168.1.12 tu peux te connecter ?
          0
        5. niconovice Auteur
          merci d'essayer :)

          nico@nico-System-Product-Name:~$ /etc/init.d/ssh status
          * sshd is running

          et sur le tel j'ai une ligne qui m'indique:
          inet 192.168.1.12 netmask 0xffffff00 broadcast 192.168.1.255

          Et pour la dernière question tu parles d'un localhost ? si c'est la question oui je peux mais le mot de passe est refusé...?

          Ps: sur un autre ordi sous windows, "putty" m'indique:
          "network error: Connection refused"
          0