From: "Soeren Laursen" <soeren.laursen@scrooge.dk>
To: George Gensure <werkt@csh.rit.edu>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: openssh probs
Date: Mon, 17 Sep 2001 18:39:30 +0200 [thread overview]
Message-ID: <3BA64362.29627.225041C@localhost> (raw)
In-Reply-To: <Pine.SOL.4.31.0109171218020.15630-100000@fury.csh.rit.edu>
> Yeah, should've mentioned the version. I'm already running 2.9p2. The
> ssh server I'm testing on, I KNOW works. I connect to it from my i686 box
> all the time. I looked at the packet dump, and it doesn't look like the
> MAC is getting sent correctly. I wasn't able to find the string anywhere
> in there (assuming it gets sent unencrypted, of course).
Running
OpenSSH_2.9p2, SSH protocols 1.5/2.0,
On a:
cpu : MIPS
cpu model : R4000SC V5.0
system type : SGI Indy
BogoMIPS : 74.75
byteorder : big endian
unaligned accesses : 0
wait instruction : no
microsecond timers : yes
extra interrupt vector : no
hardware watchpoint : yes
VCED exceptions : 27900
VCEI exceptions : 135012
It is a 2.4.3 kernel.
Nothing special running on it.
Just installed a upgrade 2.9p6
OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
And it work just as great as the first version.
Best regards,
Søren,
WARNING: multiple messages have this Message-ID (diff)
From: "Soeren Laursen" <soeren.laursen@scrooge.dk>
To: George Gensure <werkt@csh.rit.edu>
Cc: linux-mips@oss.sgi.com
Subject: Re: openssh probs
Date: Mon, 17 Sep 2001 18:39:30 +0200 [thread overview]
Message-ID: <3BA64362.29627.225041C@localhost> (raw)
Message-ID: <20010917163930.jX4risM2g2VP4rjZ5lYlsM4W11kFwAEOwTy4ARS3fLo@z> (raw)
In-Reply-To: <Pine.SOL.4.31.0109171218020.15630-100000@fury.csh.rit.edu>
> Yeah, should've mentioned the version. I'm already running 2.9p2. The
> ssh server I'm testing on, I KNOW works. I connect to it from my i686 box
> all the time. I looked at the packet dump, and it doesn't look like the
> MAC is getting sent correctly. I wasn't able to find the string anywhere
> in there (assuming it gets sent unencrypted, of course).
Running
OpenSSH_2.9p2, SSH protocols 1.5/2.0,
On a:
cpu : MIPS
cpu model : R4000SC V5.0
system type : SGI Indy
BogoMIPS : 74.75
byteorder : big endian
unaligned accesses : 0
wait instruction : no
microsecond timers : yes
extra interrupt vector : no
hardware watchpoint : yes
VCED exceptions : 27900
VCEI exceptions : 135012
It is a 2.4.3 kernel.
Nothing special running on it.
Just installed a upgrade 2.9p6
OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
And it work just as great as the first version.
Best regards,
Søren,
next prev parent reply other threads:[~2001-09-17 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 16:10 openssh probs George Gensure
2001-09-17 16:10 ` George Gensure
2001-09-17 16:16 ` Soeren Laursen
2001-09-17 16:16 ` Soeren Laursen
2001-09-17 16:20 ` George Gensure
2001-09-17 16:20 ` George Gensure
2001-09-17 16:39 ` Soeren Laursen [this message]
2001-09-17 16:39 ` Soeren Laursen
2001-09-18 3:47 ` Robin Humble
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=3BA64362.29627.225041C@localhost \
--to=soeren.laursen@scrooge.dk \
--cc=linux-mips@oss.sgi.com \
--cc=werkt@csh.rit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.