BONE and SSH

[Pete Goodeve]

It'd be nice if someone can provide some answer here, as I'm getting a
little frustrated... (:-/)

At our lab I still (!) use a BeOS machine as my main utility box, using
SSH to connect to our Linux server. Up until now, I stuck with netserver
because it was 'good enough', but now we're rearranging things so we have
two nets -- the internet and a private LAN -- and I find that two net
cards just don't work nohow noway with netserver, so I've had to switch
to BONE.

SSH seems to work with BONE... as long as I open only *one* connection!
Under netserver I habitually had multiple windows open on the same Linux
box, so being stuck with just one is a major annoyance. I've been through
all the docs I can think of to find a clue as to where the difference
might be, but I'm still lost. I suspect port numbers or the like, but
I really have no idea.

If somebody knows SSH (or BONE) well enough to point me in a good
direction, I'd be grateful. I'm using the standard 1.2.26 version on
BeOS, but we have OpenSSH 3.6.1 on Linux.

TIA,
-- Pete --

[Mikael Jansson]

Post by Pete Goodeve
It'd be nice if someone can provide some answer here, as I'm getting a
little frustrated... (:-/)
At our lab I still (!) use a BeOS machine as my main utility box, using
SSH to connect to our Linux server. Up until now, I stuck with netserver
because it was 'good enough', but now we're rearranging things so we have
two nets -- the internet and a private LAN -- and I find that two net
cards just don't work nohow noway with netserver, so I've had to switch
to BONE.

Actually, it should work as long as the NIC driver supports >1 physical
cards, and that's an issue I've heard almost exclusively with old ISA
NE2k cards.

Anyway..

Post by Pete Goodeve
SSH seems to work with BONE... as long as I open only *one*
connection!
Under netserver I habitually had multiple windows open on the same Linux
box, so being stuck with just one is a major annoyance. I've been through
all the docs I can think of to find a clue as to where the difference
might be, but I'm still lost. I suspect port numbers or the like, but
I really have no idea.

This is really odd; I'm using the OpenSSH port at BeBits, and it works
just great, port forwarding, a zillion sessions open at once etc.

Can't remember which app I downloaded though. Might've been this one, or
the OpenSSL package for BONE.

-- tic

[Pete Goodeve]

Post by Mikael Jansson

Post by Pete Goodeve
I find that two net
cards just don't work nohow noway with netserver, so I've had to switch
to BONE.

Actually, it should work as long as the NIC driver supports >1 physical
cards, and that's an issue I've heard almost exclusively with old ISA
NE2k cards.

Hmmm. The actual setup (using handy spare cards (:-)) is one PCI and
one ISA card (different makes). Sorry can't remember the model numbers
-- I'm not at the lab now. I tried everything I could think of, but it
always claims the ISA one "failed to initialize". Interestingly that is
the one I've been using all this time by itself!

Post by Mikael Jansson

Post by Pete Goodeve
SSH seems to work with BONE... as long as I open only *one*
connection!

This is really odd; I'm using the OpenSSH port at BeBits, and it works
just great, port forwarding, a zillion sessions open at once etc.
Can't remember which app I downloaded though. Might've been this one, or
the OpenSSL package for BONE.

Ahh... Now that's weird. I could have sworn I checked for an SSH2 on
BeBits, and never found it, but I looked, and thereit is! [Maybe as
I wasn't using BONE at the lab (only at home), I ignored it.] I've
been using the fairly old SSH1. I would rather standardize on OpenSSH
anyway, so it all sounds good. I'll try to plug it in next week.

And on that subject, I'd love to have sshd on the machine too [as the
campus won't allow telnet any more!], but as nobody else has done it
I assume there are obstacles. I'll probably look into that next week
as well, but if someone can tell me why I'd be wasting my time....

Thanks,
-- cPete --

[Donn Cave]

Quoth ***@jwgibbs.cchem.berkeley.edu (Pete Goodeve):
| In article <***@pip.unknown.dom>,
| Mikael Jansson <***@dtek.chalmers.se> wrote:
...
|> Can't remember which app I downloaded though. Might've been this one, or
|> the OpenSSL package for BONE.
|
| Ahh... Now that's weird. I could have sworn I checked for an SSH2 on
| BeBits, and never found it, but I looked, and thereit is! [Maybe as
| I wasn't using BONE at the lab (only at home), I ignored it.] I've
| been using the fairly old SSH1. I would rather standardize on OpenSSH
| anyway, so it all sounds good. I'll try to plug it in next week.
|
| And on that subject, I'd love to have sshd on the machine too [as the
| campus won't allow telnet any more!], but as nobody else has done it
| I assume there are obstacles. I'll probably look into that next week
| as well, but if someone can tell me why I'd be wasting my time....

There are obstacles! That goes without saying. I have never looked
at it, but one kind of basic problem with servers like this on 5.03
and earlier is that open sockets don't survive a fork. There could
be some way around it, since they made telnetd work, but anyway this
problem and probably a couple of others should go away in BONE, so
your odds are a lot better.

The ssh2 I see on BeBits is presented with a disclaimer that goes
something like `I don't know where these binaries came from ...'
I would feel kind of funny using software like that for secure
connections. Is there an OpenSSL source somewhere that builds on
BeOS? When I have tried to build OpenSSH, that's where I ran into
the wall - OpenSSH needs OpenSSL, OpenSSL needs Perl, Perl is broken.

Donn Cave, ***@drizzle.com

[Pete Goodeve]

Post by Donn Cave
| And on that subject, I'd love to have sshd on the machine too [as the
| campus won't allow telnet any more!], but as nobody else has done it
| I assume there are obstacles. I'll probably look into that next week
| as well, but if someone can tell me why I'd be wasting my time....
There are obstacles! That goes without saying. I have never looked
at it, but one kind of basic problem with servers like this on 5.03
and earlier is that open sockets don't survive a fork. There could
be some way around it, since they made telnetd work, but anyway this
problem and probably a couple of others should go away in BONE, so
your odds are a lot better.

I'll take a shot, then...

Post by Donn Cave
The ssh2 I see on BeBits is presented with a disclaimer that goes
something like `I don't know where these binaries came from ...'
I would feel kind of funny using software like that for secure
connections. Is there an OpenSSL source somewhere that builds on
BeOS? When I have tried to build OpenSSH, that's where I ran into
the wall - OpenSSH needs OpenSSL, OpenSSL needs Perl, Perl is broken.

Yes, I noticed that about those binaries, too. A bit worrying.
As it happens, I have already copied the OpenSSH sources from our
Linux machine over to BeOS, but haven't got to the point of trying
to compile yet. I brought over everything, including perl, I think.
In what way is it broken?

Cheers,
-- Pete --

[Donn Cave]

Quoth ***@jwgibbs.cchem.berkeley.edu (Pete Goodeve):
...
| As it happens, I have already copied the OpenSSH sources from our
| Linux machine over to BeOS, but haven't got to the point of trying
| to compile yet. I brought over everything, including perl, I think.
| In what way is it broken?

Don't remember the details, sorry.

Donn Cave, ***@drizzle.com