9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] server presented public key different than expected
Date: Sat, 10 Apr 2004 09:25:53 -0400	[thread overview]
Message-ID: <3A063882.56972951@mail.gmail.com> (raw)
In-Reply-To: <96ff515ffb9786a6970696e90ba4c920@mteege.de>

> server cao presented public key different than expected
> (expected key in /usr/mtg/lib/keyring).  will not continue.
> this could be a man-in-the-middle attack.
> 
> I understand the problem but there isn't any public key
> for server cao in /usr/mtg/lib/keyring. It has only two
> lines for different servers. Is there any other place where
> public keys are saved?

ssh tries to figure out the canonical names for
servers so that you don't get prompted over and
over as you use slightly different names for each
machine.

in /sys/src/cmd/ssh.c, after the call to setaliases,
put print("host aliases: %s\n", c->aliases);
perhaps one of those is matching a key in that file.

the message is accurate -- it's really that file
that has the key.

russ


      reply	other threads:[~2004-04-10 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10 12:37 Matthias Teege
2004-04-10 13:25 ` Russ Cox [this message]

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=3A063882.56972951@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).