Jeff Bailey <[EMAIL PROTECTED]> writes:
> On the client side I'm getting this:
...
> Received debug: Key exchange successful!
> User authentication failed.
> lsh: Public key userauth failed.
> Connection died, for reason 1.
> [jbailey@cr499794-a jbailey]$
>
> On the server side:
...
> Received debug: Key exchange successful!
> Unknown publickey algorithm
> Unknown publickey algorithm
> Disconnect for reason 14
> No more auth methods available
> Connection died, for reason 0.
> Connection died.
> Garbage collecting while idle...
> Objects alive: 81, garbage collected: 301
You don't say what you expected, and what the problem is... There's
one bug, now fixed by jps, that explains why lsh didn't fall back to
paasword authentication (for those of you that prefer diffs, I append
a diff below. It is the same code as jps posted here a little while
ago).
> The public key was generated today. Both the server and the client
> were just './configure; make; make check; make install' However, the
> server appears to report that the publickey algorithm is unknown
> which doesn't make sense to me.
That is somewhat expected; the client tries its keys as both "spki" keys
and "ssh-dss" keys, but for now, the server only recognizes ssh-dss.
Nevertheless, you should be able to log in using the public key (it's
one of the things actually tested by the (cd src/testsuite && make
check-more) that I do before release... So I'll need some more
information. You have run lsh-authorize on the server side?
> Per the man page, I generated the key with:
You think it is better to refer to the texinfo manual (when I get to
it, all man pages except the lsh one can probably be generated by
help2man. For the lsh man page, one should keep a hand written
introduction, and then somwhow extract the "Invoking lsh" node and
subnodes for reference). But it's not a high pririty, so perhaps the
debian maintainer will get around to it before me.
/Niels
diff -u -w -r1.38 -r1.39
--- client_userauth.c 2000/08/04 21:40:03 1.38
+++ client_userauth.c 2000/08/24 22:18:46 1.39
@@ -378,15 +378,15 @@
if ( (e->type == EXC_USERAUTH)
&& (self->state->next < LIST_LENGTH(self->state->userauth->methods)))
{
+ self->state->current = self->state->next++;
+ {
CAST_SUBTYPE(client_userauth_method, method,
LIST(self->state->userauth->methods)[self->state->current]);
- self->state->current = self->state->next;
- self->state->next++;
-
self->state->failure
= CLIENT_USERAUTH_LOGIN(method, self->state->userauth,
self->state->connection, s);
+ }
}
else
EXCEPTION_RAISE(s->parent, e);
