(SOLVED) secure ssh connection using ssh-keygen

[revslikehell]

Tweet

good evening po sa inyong lahat.. bago lang po ako sa thread...

pwde po ba manghingi ng tulong, step by step po ng ssh connection from linux mint to centos.. nagawa ko na po eh.. kaso ang problem.. nang hihingi pa din ng password.. anlabo hehe

[cerealkraker]

since nagawa n po,

try to use the verbose option (-v) and do $ ssh -v "your IP add or Domain here" possible po na ngyayari is hindi nya ginagamit or nakikita yung RSA key mo and since (i assume) naka-enable pa din yun password authentication it will proceed to the next level of authentication w/c is your password.

check mo din po ung permission ng .ssh directory mo -  if im not mistaken dapat 700 un and 644 ung .pub

[revslikehell]

thanks po sa reply kaso may error pa din

================================
ssh -v -p 8383 serverbot@192.168.56.101
OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.56.101 [192.168.56.101] port 8383.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Debian-3ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA ed:19:1d:73:0c:d3:de:f7:9a:b5:fa:5a:f1:fb:f8:35
debug1: checking without port identifier
debug1: Host '192.168.56.101' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:3
debug1: found matching key w/out port
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
Cannot determine realm for numeric host address

debug1: Unspecified GSS failure.  Minor code may provide more information
Cannot determine realm for numeric host address

debug1: Unspecified GSS failure.  Minor code may provide more information


debug1: Unspecified GSS failure.  Minor code may provide more information
Cannot determine realm for numeric host address

debug1: Next authentication method: publickey
debug1: Offering RSA public key: ariez@ariez-Lenovo-IdeaPad-U330
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Offering RSA public key: /root/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Trying private key: /root/.ssh/id_ecdsa
debug1: Next authentication method: password
================================

meron akong nasaba sa forum - uncomment ko daw ito sa sshd_conf na file "GSSAPIAuthentication no"

nawala mga unspecified GSM failure pero nag hahanap pa din ng password.. skit na ng ulo ko dito.. amf

[cerealkraker]

nangyari n din sa kin dati yan, (medyo matagal na talga :) ) it has something to do with the user profile mismo, if my memory serves me right, parang chineck ko pa ung shadowcopy ng password something like that - dont qoute me on that baka mali aq :)

*try mo create ka ng bagong user and cyempre dont forget the password and to generate rsa key - then temporarily un muna gamitin mo.

[vjbangis]

Sir, may I ask kung pagdating dito

Enter passphrase (empty for no passphrase): [Press enter key]
Enter same passphrase again: [Pess enter key]

is wala ka pong nilagay na password?

kung wala 

then, copy the .ssh/id_rsa.pub from host pc to remote pc and change it to .ssh/authorized_keys.

hope this could help.

[revslikehell]

mga idol.. thanks po.. na resolve ko na..

ganito po pala cya.. dapat di ako gagawa ng .ssh/authorized_keys na folder

ganito po ang command na ginamit ko

scp id_rsa.pub serverbot@192.168.56.100:/home/serverbot

then

"cat id_rsa.pub >> .ssh/autorhized_keys"

yan po pala ang dapat.. ^

hindi pala  cya direct sa serverbot@192.168.56.100:/home/serverbot/.ssh/authorized_keys

pano po i modify yung subject as SOLVED...