Kunna Yanayin gyara kurakurai a cikin SSH zuwa Shirya Matsalar Haɗuwa


A cikin wannan labarin, za mu nuna muku yadda ake kunna yanayin lalata yayin gudanar da SSH a Linux. Wannan zai ba ku damar ganin abin da ke faruwa a zahiri lokacin da kuka aiwatar da umarnin ssh don haɗawa zuwa uwar garken Linux mai nisa ta amfani da yanayin verbose ko yanayin lalata.

Maɓallin -v abokin ciniki na ssh yana ba ku damar gudanar da ssh a cikin yanayin magana, wanda ke buga bayanan lalata game da ci gaban haɗin SSH, wanda ke da matukar amfani don cire haɗin haɗin yanar gizo, tantancewa, da kowane matsala na daidaitawa. Akwai matakan magana daban-daban; ta amfani da tutoci masu yawa -v yana ƙara yawan magana (mafi girman matakin magana shine 3).

Umurnin da ke biyowa zai gudanar da SSH a matakin farko na magana, wanda ke ba mu bayanai masu yawa na lalata kamar yadda aka nuna.

[email  ~ $ ssh -v [email 
OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g-fips  1 Mar 2016
debug1: Reading configuration data /home/aaronkilik/.ssh/config
debug1: /home/aaronkilik/.ssh/config line 18: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.56.10 [192.168.56.10] port 22.
debug1: Connection established.
debug1: identity file /home/aaronkilik/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaronkilik/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaronkilik/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaronkilik/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaronkilik/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaronkilik/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaronkilik/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/aaronkilik/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
debug1: match: OpenSSH_7.4 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.56.10:22 as 'tecmint'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: [email 
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: [email  MAC:  compression: [email 
debug1: kex: client->server cipher: [email  MAC:  compression: [email 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:1778erqyug4tHJa7D6y/Ep4UWsUtNEOBSMaj32k9oO8
debug1: Host '192.168.56.10' is known and matches the ECDSA host key.
debug1: Found key in /home/aaronkilik/.ssh/known_hosts:8
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/aaronkilik/.ssh/id_rsa
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug1: Enabling compression at level 6.
debug1: Authentication succeeded (publickey).
Authenticated to 192.168.56.10 ([192.168.56.10]:22).
debug1: channel 0: new [client-session]
debug1: Requesting [email 
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype [email  want_reply 0
debug1: Sending environment.
debug1: Sending env LC_PAPER = lg_UG.UTF-8
debug1: Sending env LC_ADDRESS = lg_UG.UTF-8
debug1: Sending env LC_MONETARY = lg_UG.UTF-8
debug1: Sending env LC_NUMERIC = lg_UG.UTF-8
debug1: Sending env LC_TELEPHONE = lg_UG.UTF-8
debug1: Sending env LC_IDENTIFICATION = lg_UG.UTF-8
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending env LC_MEASUREMENT = lg_UG.UTF-8
debug1: Sending env LC_NAME = lg_UG.UTF-8
Last login: Sat Jan  6 16:20:11 2018 from 192.168.56.1

Lokacin ƙoƙarin fita ko fita zaman, za ku kuma ga saƙonnin kuskure kamar yadda aka nuna.

[[email  ~]$ exit

logout
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow[email  reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to 192.168.56.10 closed.
Transferred: sent 3392, received 3120 bytes, in 118.1 seconds
Bytes per second: sent 28.7, received 26.4
debug1: Exit status 0
debug1: compress outgoing: raw data 1159, compressed 573, factor 0.49
debug1: compress incoming: raw data 573, compressed 1159, factor 2.02

Na gaba, zaku iya kunna ƙarin (matakin 2 da 3) magana mai ƙarfi don ƙarin saƙon kuskure kamar yadda aka nuna.

$ ssh -vv [email 
$ ssh -vvv [email 

Shi ke nan! Don ƙarin amfani da SSH, karanta waɗannan labarai masu alaƙa.

  1. Yadda ake Nemo Duk Ƙoƙarin shiga SSH da bai yi nasara ba a cikin Linux
  2. Yadda ake kashe Tushen SSH a Linux
  3. SSH Password Shigar Amfani da SSH Keygen a cikin Sauƙaƙe Matakai 5
  4. Yadda ake cire haɗin haɗin SSH mara aiki ko mara aiki a cikin Linux

Muna fatan wannan labarin ya taimaka. Kuna iya yin kowace tambaya ko raba tunani ta hanyar sharhin da ke ƙasa.