ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Mikhail Zabaluev <mhz@alt-linux.org>
To: devel@altlinux.ru
Subject: [devel] Re: Key changed on altair?
Date: Sat, 5 Jan 2002 15:45:42 +0300
Message-ID: <20020105124542.GE1763@mhz.mikhail.zabaluev.name> (raw)
In-Reply-To: <3C36E392.20703@altlinux.ru>

[-- Attachment #1: Type: text/plain, Size: 3089 bytes --]

Hello Anton,

On Sat, Jan 05, 2002 at 02:29:22PM +0300, Anton Farygin wrote:
>
> Mikhail Zabaluev wrote:
> 
> >Доброго времени суток.
> >
> >Как это понимать?
> >
> >[mhz@localhost mhz]$ ssh altair
> >The authenticity of host 'altair.altlinux.ru (194.67.87.171)' can't be
> >established.
> >RSA key fingerprint is
> >d7:9b:f1:f5:e3:cb:63:a1:3b:d8:fa:57:2f:38:1c:9a.
> >Are you sure you want to continue connecting (yes/no)?
> >
> Вчера Дима поставил новый OpenSSH.
> 
> Но ключи не менялись.
> 
> Rgds,
> Rider
> 
> P.S. А почему RSA а не DSA?

Не имею понятия. Вот выдержка из .ssh/config:

Host altair
    HostName altair.altlinux.ru
    Protocol 2
    Compression yes
    CompressionLevel 9
    IdentityFile ~/.ssh/id_altair

Лог соединения с -v (я до этого принял новый ключ сервера):

OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /home/mhz/.ssh/config
debug1: Applying options for altair
debug1: Reading configuration data /etc/openssh/ssh_config
debug1: Seeding random number generator
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 altair.altlinux.ru [194.67.87.171] port 22.
debug1: temporarily_use_uid: 501/501 (e=501)
debug1: restore_uid
debug1: temporarily_use_uid: 501/501 (e=501)
debug1: restore_uid
debug1: Connection established.
debug1: identity file /home/mhz/.ssh/id_altair type 2
debug1: Remote protocol version 2.0, remote software version
OpenSSH_3.0.2p1
debug1: match: OpenSSH_3.0.2p1 pat ^OpenSSH
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_2.9p2
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: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 131/256
debug1: bits set: 1608/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'altair.altlinux.ru' is known and matches the RSA host
key.
debug1: Found key in /home/mhz/.ssh/known_hosts2:8
debug1: bits set: 1616/3191
debug1: ssh_rsa_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: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue: publickey,password
debug1: next auth method to try is publickey
debug1: userauth_pubkey_agent: testing agent key dsa w/o comment
debug1: input_userauth_pk_ok: pkalg ssh-dss blen 817 lastkey 0x8093bd8
hint -1
debug1: ssh-userauth2 successful: method publickey

-- 
Stay tuned,
  MhZ                                     JID: mookid@jabber.org
___________
There is no such thing as fortune.  Try again.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-01-05 12:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 22:35 [devel] " Mikhail Zabaluev
2002-01-04 23:16 ` Aleksey Novodvorsky
2002-01-05 11:29 ` Anton Farygin
2002-01-05 12:45   ` Mikhail Zabaluev [this message]
2002-01-08 15:27   ` Dmitry V. Levin
2002-01-08 20:42     ` [devel] " Mikhail Zabaluev
2002-01-09  9:33       ` [devel] " Dmitry V. Levin

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=20020105124542.GE1763@mhz.mikhail.zabaluev.name \
    --to=mhz@alt-linux.org \
    --cc=devel@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 Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/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 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git