* Markus Grunwald ([EMAIL PROTECTED]) spake thusly:
> Hi !
>
> First of all: congrats to your success :)
>
> > meh. keeping this short. I'm an idiot, kinda. :)
> > SSH is a complicated mess, that's my excuse.
>
> Thats the point.
> I tried to do some things with ssh as well and was desperately s
Hi !
First of all: congrats to your success :)
> meh. keeping this short. I'm an idiot, kinda. :)
> SSH is a complicated mess, that's my excuse.
Thats the point.
I tried to do some things with ssh as well and was desperately searching
for some understandable manual. The manpages may handle every
meh. keeping this short. I'm an idiot, kinda. :)
SSH is a complicated mess, that's my excuse. Basically, this sums it up:
RSA = v2 (*not* v1)
RSA1 = v1
DSA = v2
So, when I said it was doing v1 when it should be v2, I meant it was
doing RSA when it should be doing DSA. And then realized th
On Mon, Sep 17, 2001 at 10:32:36AM +0200, Pietro Cagnoni wrote:
> ...
>
> i've always been able to solve my ssh problems using sshd -d and ssh -v
doh. yeah, I probably tried that. but now I've poked at it some more.
sshd -d -d -d, all protocols enabled:
not very interesting. just so you know w
> Still interested in comments if anybody's got any. :)
uh, maybe you already did that, but...
i've always been able to solve my ssh problems using sshd -d and ssh -v
hope it helps
pietro.
Eh. Ok. With some more banging on it, RSA auth sort of works now.
Before, I don't think protocol v1 was working with RSA auth, and v2
didn't work at all. However, disabling v1 altogether and generating
new v2 keys for RSA auth works. Connect. Yay. Happy.
But the protocol resolution or somethin
I've been having a couple annoying problems with ssh, current version
in unstable. First off is, sshd absolutely refuses to use protocol v2,
either with the default 2,1 or explicitly setting 2,1 or using ssh -2
to connect. The only way I got it to use v2 was to disable completely
v1, which I r
7 matches
Mail list logo
