SSH 22

de data asta asa scire...:


cat /var/log/secure
Apr 17 15:19:23 localhost sshd[560]: Server listening on 0.0.0.0 port 22.
Apr 17 15:20:25 localhost sshd[560]: Received signal 15; terminating.
Apr 17 15:33:41 localhost sshd[570]: Server listening on 0.0.0.0 port 22.
Apr 17 15:36:46 localhost sshd[570]: Received signal 15; terminating.
Apr 17 15:41:47 localhost sshd[571]: Server listening on 0.0.0.0 port 22.
Apr 17 15:43:42 localhost sshd[571]: Received signal 15; terminating.
Apr 17 15:46:54 localhost sshd[571]: Server listening on 0.0.0.0 port 22.
Apr 17 17:06:13 localhost sshd[539]: Server listening on 0.0.0.0 port 22.
Apr 17 17:06:58 localhost sshd[539]: Received signal 15; terminating.
Apr 17 17:12:19 localhost sshd[689]: Server listening on 0.0.0.0 port 22.
Apr 17 17:49:31 localhost sshd[689]: Received signal 15; terminating.
Apr 17 17:52:54 localhost sshd[717]: Server listening on 0.0.0.0 port 22.
Apr 17 20:54:39 localhost sshd[717]: Received signal 15; terminating.
Apr 17 20:58:06 localhost sshd[717]: Server listening on 0.0.0.0 port 22.
Apr 17 22:47:21 localhost sshd[727]: Server listening on 0.0.0.0 port 22.
Apr 17 23:04:52 localhost sshd[727]: Received signal 15; terminating.
Apr 17 23:08:27 localhost sshd[716]: Server listening on 0.0.0.0 port 22.
Apr 19 01:20:11 localhost sshd[663]: Server listening on 0.0.0.0 port 22.
Apr 19 01:24:48 localhost sshd[572]: Server listening on 0.0.0.0 port 22.
Apr 19 01:32:48 localhost sshd[671]: Server listening on 0.0.0.0 port 22.
Apr 19 01:34:45 localhost sshd[671]: Received signal 15; terminating.
Apr 19 01:50:28 localhost sshd[714]: Server listening on 0.0.0.0 port 22.
Apr 19 02:00:08 localhost sshd[711]: Server listening on 0.0.0.0 port 22.
Apr 19 02:03:02 localhost sshd[618]: Server listening on 0.0.0.0 port 22.
Apr 19 02:04:20 localhost sshd[618]: Received signal 15; terminating.
Apr 19 02:16:15 localhost sshd[833]: Server listening on 0.0.0.0 port 22.
Apr 19 09:19:00 localhost sshd[731]: Server listening on 0.0.0.0 port 22.
Apr 19 09:33:54 localhost sshd[953]: error: Bind to port 22 on 0.0.0.0 failed: A
ddress already in use.
Apr 19 09:33:54 localhost sshd[953]: fatal: Cannot bind any address.
Apr 19 10:17:10 localhost sshd[730]: Server listening on 0.0.0.0 port 22.
Apr 19 11:02:59 localhost sshd[731]: Server listening on 0.0.0.0 port 22.
Apr 19 11:09:20 localhost sshd[936]: Server listening on 0.0.0.0 port 22.

ce sa fac ??? dar daca tot nu merge ssh 22 pot sa deshid macat telnetu 23 ????  cum ?
mercy

Dupa ce incearca sa faci ssh pe masina respectiva, uita-te in /var/log/messages dupa ssh si vezi ce zice.

Edited by mufa, 19 April 2005 - 10:34.

sunt foarte numte ... mesaje (linii) in  /var/log/messages


eu ti le atay pe ultimele... ca daca ma-s apuka sa le pun pe toate ar ocupa toto forumu ..

Apr 19 11:06:27 localhost kernel: eth1: link up.
Apr 19 11:06:27 localhost kernel: eth1: Setting full-duplex based on negotiated link capability.
Apr 19 11:06:28 localhost /etc/hotplug/net.agent: invoke ifup eth1
Apr 19 11:09:20 localhost sshd:  succeeded
Apr 19 11:11:12 localhost login(pam_unix)[825]: session closed for user root
Apr 19 11:34:18 localhost sshd:  succeeded


??

GabyBoy, on Apr 19 2005, 11:39, said:

ssh -v localhost arata ceva interesant?

asa zice... :

ssh -v localhost
OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.4p1
debug1: match: OpenSSH_3.4p1 pat OpenSSH*
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.4p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 124/256
debug1: bits set: 1582/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
The authenticity of host 'localhost (127.0.0.1)' can't be established.
RSA key fingerprint is b0:f6:89:94:38:63:10:42:98:2e:c8:83:cc:20:8d:02.
Are you sure you want to continue connecting (yes/no)? yes
yes

Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
debug1: bits set: 1631/3191
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try privkey: /root/.ssh/identity
debug1: try privkey: /root/.ssh/id_rsa
debug1: try privkey: /root/.ssh/id_dsa
debug1: next auth method to try is keyboard-interactive
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: next auth method to try is password
[email protected]'s password:

debug1: ssh-userauth2 successful: method password
debug1: channel 0: new [client-session]
debug1: send channel open 0
debug1: Entering interactive session.
debug1: ssh_session2_setup: id 0
debug1: channel request 0: pty-req
debug1: channel request 0: shell
debug1: fd 3 setting TCP_NODELAY
debug1: channel 0: open confirm rwindow 0 rmax 32768
Last login: Tue Apr 19 11:03:46 2005
No value for $TERM and no -T specified
No value for $TERM and no -T specified



ce sa fac ma ??? ori sa deshid ssh 22 ori telnet 23 ... asta vreu. ce sa fac ??????? pls

Daca incerci sa faci ssh pe masina respectiva de pe alta masina, ce se intimpla ?
Porneste si sshd-ul in debug mode si vezi ce se intimpla.

Edited by mufa, 19 April 2005 - 11:45.

nu inteleg ce vreis a zici

posibil sa nu te lase sa te loghezi ca root
ssh [email protected]

posibil sa nu te lase sa te loghezi de pe loopback/IP-ul masiniii; de pe o alta masina incearca:
ssh [email protected]

SSH merge la tine, trebuie sa verifici si ca nu ai vreun firewall prin zona.

ok... acum o s avad ms..

salut... Nustiu ce sa fac... am incercat din nou sa deshid ssh`ul 22... merge zice [OK] Dar cand incerc sa intru pe portu ala nu merge (( ce se intampla... dc nu se deshide... sau dc nu merge sa intru pe portu ala ??! ce sa fac ??! mercy... poate de data asta gasim raspunsul la aceasta intrtebare care ma framanta de multa vreme ... se poate ca sa existe firewall sis a nu dea voie sa intru pe portu ala ??? cum il scot.. sa imi dea voie sa intru ?? mercy  mult tuturor !!!!!

aha... am aflat ceva... am dat asa:  ssh 10.13.0.1

si s-a conectat ...

Last login: Sun Apr 24 03:58:25 2005 from 10.13.0.1
No value for $TERM and no -T specified
No value for $TERM and no -T specified
[[email protected] root]# ps x

ma-m logat ca root.. dar acum nustiu cum sa deschid port pe ssh sa ma loghez direct.. acum am bind deschis pe telnet si nu imi convine sa imi intre toti in el

10.13.0.1 fiind ipul de pe server


stie cineva ce sa fac ?? sa mearga ssh`ul ?

oooooooooooooooooooooooof gramatica asta bat-o vina...

GabyBoy, on Apr 24 2005, 03:57, said:

Probabil tu îți închipui ca ești "jmeker", dar să știi că mercy înseamnă milă în engleză....
Ori folosești clasicul mulțumesc, ori mersi, sau franțuzescul merci...

dar tu esti smecher ma ?
mai bine taci !

GabyBoy, on Apr 24 2005, 10:54, said:

[OT]
Atentie la limbaj. Valabil si pt tine si pt retele care sper sa nu se lase antrenat in flame. Oricum, din pctul meu de vedere sa stii ca retele are un punct de vedere intemeiat.[/OT]

Revenind, ai cautat sa vezi daca nu cumva ai firewall intre tine si server? Ai incercat sa te legi de la consola prin ssh?Ti-am spus ca e posibil ca login-ul de root sa fie dezactivat (si pe buna dreptate). Creaza un cont de user normal, te loghezi  ca [email protected] si apoi folosesti su sau sudo ca sa obtii drepturi de root.

Edited by cianura, 24 April 2005 - 11:59.

cred ca nu voi reusi niciodata sa deshid ssh`ul 22 (  nustiu ma cums a scot firewallu ala care nu imi da voie sa ma loghez pe ssh 22