From: Andrey Brindeew <linux@abr.pp.ru> To: ALTLinux Mailing List <mandrake-russian@altlinux.ru> Subject: [mdk-re] Авторизация по ключам, ssh2 Date: Fri Apr 5 11:04:14 2002 Message-ID: <20020405110623.69fafbc2.linux@abr.pp.ru> (raw) [-- Attachment #1: Type: text/plain, Size: 2577 bytes --] Hi! Попробовал тут провернуть штуку (на lrn недавно ссылка на howto пролетала). По ssh1 все работает, а вот с ssh2 не срослось. Это серверные проблемы или мои? $ ssh -2 -C -v USERNAME@HOST.RU OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /etc/openssh/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 501 geteuid 501 anon 1 debug1: Connecting to HOST.RU [XXX.XXX.XXX.XXX] port 22. debug1: temporarily_use_uid: 501/503 (e=501) debug1: restore_uid debug1: temporarily_use_uid: 501/503 (e=501) debug1: restore_uid debug1: Connection established. debug1: identity file /home/LOCAL_USERNAME/.ssh/id_rsa type -1 debug1: identity file /home/LOCAL_USERNAME/.ssh/id_dsa type 2 debug1: Remote protocol version 1.99, remote software version 2.0.13 (non-commercial) debug1: match: 2.0.13 (non-commercial) pat 2.0.13*,2.0.14*,2.0.15*,2.0.16*,2.0.17*,2.0.18*,2.0.19* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.1p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client blowfish-cbc hmac-md5 zlib debug1: kex: client->server blowfish-cbc hmac-md5 zlib debug1: dh_gen_key: priv key bits set: 136/256 debug1: bits set: 531/1024 debug1: sending SSH2_MSG_KEXDH_INIT debug1: expecting SSH2_MSG_KEXDH_REPLY debug1: Host 'HOST.RU' is known and matches the DSA host key. debug1: Found key in /home/LOCAL_USERNAME/.ssh/known_hosts2:5 debug1: bits set: 478/1024 debug1: ssh_dss_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: Enabling compression at level 6. 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: buggy server: service_accept w/o service debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password debug1: next auth method to try is publickey debug1: try privkey: /home/LOCAL_USERNAME/.ssh/id_rsa debug1: try pubkey: /home/LOCAL_USERNAME/.ssh/id_dsa debug1: authentications that can continue: publickey,password debug1: next auth method to try is password USERNAME@HOST.RU's password: P.S. А чем ssh1 от ssh2 отличается? Может не стоит возиться (тем более, что служба поддержки хостера заявляет что "авторизация по ключам выключена") и работать по ssh1? -- WBR, Andrey Brindeew. "No one person can understand Perl culture completely" (C) Larry Wall. [-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-04-05 11:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-05 11:04 Andrey Brindeew [this message] 2002-04-06 1:48 ` [mdk-re] " Michael Shigorin 2002-04-07 0:09 ` [mdk-re] " Andrey Brindeew 2002-04-08 0:43 ` [mdk-re] " Michael Shigorin 2002-04-08 1:22 ` Andrey Brindeew 2002-04-08 12:18 ` Michael Shigorin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020405110623.69fafbc2.linux@abr.pp.ru \ --to=linux@abr.pp.ru \ --cc=mandrake-russian@altlinux.ru \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git