sshd binaries
skinnypuppy
anyone know where i can get a version of ssh that is already compiled?
SP
Brian K. White
"skinnypuppy" <skin...@asd.com> wrote in message
news:3beb48fa...@news.rdc1.az.home.com...
>
> anyone know where i can get a version of ssh that is already compiled?
"gods gift, maggots!" mmm pure art...
I'm currently using
ftp://ftp.celestial.com/pub/sco-ports/unix_3_2v5/RPMS/i386/ssh-1.2.31-1.i386
.rpm
but be warned this requires installing rpm first, also available from the
same place. the installation is not exactly smooth, but not exactly a big
deal either, it's just that you are required to figure it out, it won't just
go all by itself.
--
Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
Bob Meyers
"Brian K. White" <br...@aljex.com> wrote in message
news:lKKG7.95396$ez.12...@news1.rdc1.nj.home.com...
> > anyone know where i can get a version of ssh that is already compiled?
>
>
ftp://ftp.celestial.com/pub/sco-ports/unix_3_2v5/RPMS/i386/ssh-1.2.31-1.i386
> .rpm
>
> but be warned this requires installing rpm first, also available from the
> same place. the installation is not exactly smooth, but not exactly a big
> deal either, it's just that you are required to figure it out, it won't
just
> go all by itself.
>
If it is the same one I downloaded from there, before you try to install rpm
for SCO, make a directory named "/var/tmp". And after you have installed the
rpm module, install the sshd rpm with "--nodeps" option. I think you also
must have /bin/bash, in exactly that location before installing it.
Jean-Pierre Radley
Why stick with that rather oldish ssh version, when openssh-2.9.9
compiles quite handily on OSR 5.0.6?
--
JP
Bob Meyers
"Jean-Pierre Radley" <j...@jpr.com> wrote in message
news:20011109223...@jpradley.jpr.com...
Compiler sissies will do anything to avoid it :)
Ah, but I'll have to give that one a try. There is great simplicity and
benefit in the RPM idea though. Not everyone has skills required for the
often necessary makefile hacks, etc. But now we know otherwise.
Bob Meyers
> compiles quite handily on OSR 5.0.6?
Please note my comments that follow only applies if you have a lower vesion
than 5.0.6. I happen to have the ancient history version known as 5.0.5 here
in house. I bow to JP's expertise on 5.0.6. I still am wonder however if JP
has made other assumptions about dependencies he already has installed.
Ok, now this admitted NOVICE is now 1.5 hours into trying to get it to
compile on a 5.0.5 with both cc and gcc, I can comment.
I want to use a phrase I have heard from you JP: BULLSHIT!
For the guy who posted the question: I would assume since you asked for
binaries, you might be sort of like me (AND THE VAST MAJORITY) - you are NOT
a frigging expert at building and installing libs, hacking makefiles,
installing dependencies, etc. etc. I'll bet you just hoped there was a way
for the common person to install a recognized industry standard technology,
such as sshd, on your SCO Unix box, right?
If that is the case, I would recommend you download the RPM stuff from
Celestial and do what I suggested. Shoooo, no wonder I call my self a
compiler sissy. That old version of SSH is likely to have security flaws,
but is apparently is the best we can do for the vast majority of us who
don't have a high degree of expertise. I can't find a newer one anywhere.
Thanks so much to Bill at Celestial for making that work available to us
common folk.
You know, I think Caldera should hire Bill Campbell has the new CEO for the
OpenServer division. As we all sit and watch OpenServer die on the vine and
Linux and everything else take over, maybe those of authority should ask
"What do consumers of our product want?".
Now. I will go take a valium (as if I had one), and play with my Linux box
that either comes with all that popular, industry standard shit already
included, or has a simple mechanism, called RPM for all us common folk to
install it.
BTW, <g>
skinnypuppy
I have 5.0.5., so it sounds like the compile won't go so smoothly? I
don't have the patience or attention span to slave hours at a command
prompt anymore. Give it to me in a VOL or RPM so I can intall it and
get on with my life. Anyway, I orderd 5.0.6. yesterday, so maybe I'll
just wait till it comes in.
However, I may just try the RPM and see what I get. I'm just doing
this to prove to the Linux bigots at work that ssh on OpenServer
works, even though they told the director it doesn't...
Thanks for the pointers!
SP
Richard Howlett
>
> "Jean-Pierre Radley" <j...@jpr.com> wrote in message
> news:20011109223...@jpradley.jpr.com...
> >
> > Why stick with that rather oldish ssh version, when openssh-2.9.9
> > compiles quite handily on OSR 5.0.6?
>
> Please note my comments that follow only applies if you have a lower vesion
> than 5.0.6. I happen to have the ancient history version known as 5.0.5 here
> in house. I bow to JP's expertise on 5.0.6. I still am wonder however if JP
> has made other assumptions about dependencies he already has installed.
>
> Ok, now this admitted NOVICE is now 1.5 hours into trying to get it to
> compile on a 5.0.5 with both cc and gcc, I can comment.
Ditto. I spent a whole evening doing exact same thing. Except I don't
consider myself a novice... ;-)
Trying to compile ssh on 5.0.5 with both cc and gcc. Problem after problem
after problem. I gave up in the end and copied over the binaries I had
created on our 5.0.2 system earlier that day! Works fine.
If you *REALLY* *REALLY* want my ssh binaries drop me a mail and I'll pop
them up to my website in an archive for you to download.
One thing to note is that you need to have SSL already installed and the
zlib package for ssh to compile.
--
Richard Howlett
mailto:ric...@howie.org.uk
Richard Howlett
>
> I have 5.0.5., so it sounds like the compile won't go so smoothly? I
> don't have the patience or attention span to slave hours at a command
> prompt anymore. Give it to me in a VOL or RPM so I can intall it and
> get on with my life. Anyway, I orderd 5.0.6. yesterday, so maybe I'll
> just wait till it comes in.
>
> However, I may just try the RPM and see what I get. I'm just doing
> this to prove to the Linux bigots at work that ssh on OpenServer
> works, even though they told the director it doesn't...
I can confirm that it works very nicely indeed. OpenServer to OpenServer,
RedHat 7.0 to OpenServer (and vice versa). I use it to create a secure
tunnel:
ssh -f -N -C -l richard -L 1234:localhost:23 123.456.789.123
and then once it has authenticated I:
telnet 123.456.789.123 1234
Bob Meyers
> However, I may just try the RPM and see what I get. I'm just doing
> this to prove to the Linux bigots at work that ssh on OpenServer
> works, even though they told the director it doesn't...
>
OMHO, I'll tell you what I am doing, I have been using/converting to RedHat
6.2 and 7.1. Although I am new to it, take a look at the product Tony
Lawrence talks about called e-smith (www.e-smith.com). I see it has a lot to
offer me and my clients. I am tiring of chasing security exploits, viruses,
so are my customers. This e-smith product claims to be able to handle all
that automatically if you subscribe. Your Linux biggots have a very good
point. For background on my point of view, I have been
using/selling/supporting SCO since the days of Xenix 1.0 on Altos, uh around
1982 I think. I truly have a deep, long time affection for OpenServer. But I
am about to throw in the towel on that product after all these years. Its
too bad, OpenServer COULD be the BEST one around if they had a little
different point of view.
Tony Lawrence
Just to correct any possibly wrong impression here: E-Smith is a nice
product. but it's specifically a internet gateway/proxy/email/file/print
server, not a general purpose application server like SCO. And while
it's very nicely done, it isn't nirvana either. I'd rather it than
Exchange any day, and 'd rather it than roll my own Linux solution as I
used to do, but "good" is not "perfect".
I have put a few clients on Red Hat for Counterpoint and Filepro, but
that world isn't all rosy and wonderful either. For example, while I
have yet to experience any problem with th Red Hat Update Agent, I have
a customer who reported that it messed up a test machine horribly.
SCO has it's problems, but so does everybody else. Different problems,
but still problems.
--
Tony Lawrence
SCO/Linux Support Tips, How-To's, Tests and more: http://pcunix.com
Bob Meyers
"Tony Lawrence" <to...@pcunix.com> wrote in message
news:3BEE753E...@pcunix.com...
> SCO has it's problems, but so does everybody else. Different problems,
> but still problems.
After my spell of ranting, I went out and raked leaves in the yard and
thought maybe someone should come out with a general purpose add-on or
service to OpenServer that adds services like sshd, mail services and
security patches and the latest, industry standard utilities.... sort of
like e-smith adds on to RedHat. If someone had a package that would add that
stuff to a standard SCO OpenServer Enterprise at a reasonable price I sure
would buy it! I am still chicken to put Linux in a big organization as a
critical application server - OpenServer has proven itself in that arena.
Bill Vermillion
Bob Meyers <oregon...@yahoo.com> wrote:
There is nothing that says you have to have only one server.
The E-smith [or any other front end] can be ahead of your
application server. Make that a gateway, run your sshd, mail, web,
etc., and pass through to the SCO only things that need to be
passed through.
To me it makes sense to put your mail and related system utilities
away from the main application server. I'd not like to do it any
other way.
- bill -
And here I thought that custom did that.
Oh !, you mean that someone at Caldera/SCO is supposed to be supporting
us ?
--
-bill-
Technical Service Systems - bi...@TechServSys-garbage.com
Bob Meyers
"Bill Vermillion" <b...@wjv.com> wrote in message news:GMnH8...@wjv.com...
>
> There is nothing that says you have to have only one server.
>
I have yippy-yapped too much in this thread anyway, but one more...
I do employ that strategy Bill.
Don't forget you need ssh inside the private net too due to sniffers,
trojans, backdoor servers. I have already seen one case personally where a
new PC came from a manufacturer with a BDS infection.
Ian Peattie
>Bob Meyers propounded (on Fri, Nov 09, 2001 at 11:52:59AM -0800):
>|
>| "Brian K. White" <br...@aljex.com> wrote in message
>| news:lKKG7.95396$ez.12...@news1.rdc1.nj.home.com...
>| > > anyone know where i can get a version of ssh that is already compiled?
>| >
>| > I'm currently using
>| >
>| ftp://ftp.celestial.com/pub/sco-ports/unix_3_2v5/RPMS/i386/ssh-1.2.31-1.i386
>| > .rpm
>Why stick with that rather oldish ssh version, when openssh-2.9.9
>compiles quite handily on OSR 5.0.6?
For those who like to keep right up to date, OpenSSH 3.0 was released
last week.
Ian.
--
Ian Peattie i...@john-richard.co.uk
Edinburgh, Scotland.
Ben Rosenthal
Bravo.
Ben
Bill Vermillion
Bob Meyers <oregon...@yahoo.com> wrote:
>Now. I will go take a valium (as if I had one), and play with
>my Linux box that either comes with all that popular, industry
>standard shit already included, or has a simple mechanism, called
>RPM for all us common folk to install it.
If you'd ever used the install programs on SGI - or the ports
system on FreeBSD you'd grow to hate RPM's in a hurry. At least
I did.
Installing software shouldn't be painful.
Tony Lawrence
>
> "Jean-Pierre Radley" <j...@jpr.com> wrote in message
> news:20011109223...@jpradley.jpr.com...
> >
> > Why stick with that rather oldish ssh version, when openssh-2.9.9
> > compiles quite handily on OSR 5.0.6?
>
> Please note my comments that follow only applies if you have a lower vesion
> than 5.0.6. I happen to have the ancient history version known as 5.0.5 here
> in house. I bow to JP's expertise on 5.0.6. I still am wonder however if JP
> has made other assumptions about dependencies he already has installed.
>
> Ok, now this admitted NOVICE is now 1.5 hours into trying to get it to
> compile on a 5.0.5 with both cc and gcc, I can comment.
That sort of thing is at least part of why I switched my home desktop
machine to Linux. It's not that it is impossible to compile things on
OSR5, but it is often just too damn difficult. It's not directly SCO's
fault, of course: folks who write makefiles aren't likely to think about
SCO at all, and if they do, they certainly aren't going to take care to
account for whether you have the gcc compiler or the SCO or the UDK.
And that means work for you, work that I certainly have no interest in
most of the time.
Boyd Lynn Gerber
> Bob Meyers wrote:
> > "Jean-Pierre Radley" <j...@jpr.com> wrote in message
> > news:20011109223...@jpradley.jpr.com...
> > > Why stick with that rather oldish ssh version, when openssh-2.9.9
> > > compiles quite handily on OSR 5.0.6?
> > Please note my comments that follow only applies if you have a lower vesion
> > than 5.0.6. I happen to have the ancient history version known as 5.0.5 here
> > in house. I bow to JP's expertise on 5.0.6. I still am wonder however if JP
> > has made other assumptions about dependencies he already has installed.
> That sort of thing is at least part of why I switched my home desktop
> machine to Linux. It's not that it is impossible to compile things on
> OSR5, but it is often just too damn difficult. It's not directly SCO's
> fault, of course: folks who write makefiles aren't likely to think about
> SCO at all, and if they do, they certainly aren't going to take care to
> account for whether you have the gcc compiler or the SCO or the UDK.
> And that means work for you, work that I certainly have no interest in
> most of the time.
I agree totally. I have been fighting with the openssh-3.0p1 with gcc on
OSR 5.0.6a with all the patches installed. I am using one of the latest
snapshots of openssl. It has all the patches in that fixes a lot of the
problems with entropy gathering in it. I do not have any problems with
this version of openssl with any other program. It appears that the test
for openssl is in this version of openssh is getting a missing symbol
__register_frame_info. See below ...
It is probably some option is missing in the test causing it. I just have
to figure out what. I have tried many.
configure:8191: gcc -o conftest -g -O2 -Wall -Wpointer-arith
-Wno-uninitialized -I/usr/local/ssl/include -I/usr/local/include
-L/usr/local/ssl/lib -L/usr/local/lib conftest.c -lz -lsocket -lprot
-lx -ltinfo -lm -lcrypto >&5
configure:8194: $? = 0
configure:8196: ./conftest
dynamic linker: ./conftest: symbol not found: __register_frame_info
./configure: 17265 Killed
configure:8199: $? = 137
configure: program exited with status 137
configure: failed program was:
#line 8176 "configure"
#include "confdefs.h"
#include <string.h>
#include <openssl/rand.h>
int main(void)
{
char a[2048];
memset(a, 0, sizeof(a));
RAND_add(a, sizeof(a), sizeof(a));
return(RAND_status() <= 0);
}
I often have to change configure.in or other files to get them to work
with the Caldera(SCO) OS's. It does get to be a real pain at times. But
I guess I must be into pain, I keep thinking some day they (SCO) Caldera
or who ever owns OpenServer, UnixWare, and OpenUNIX is going to wake up
and get it right. I have been doing this since the first days. I
had a xenix for the IBM PC. I have since lost it. But I do have a 286
version still. I have always loved the stability of the SCO/Caldera OS's.
So maybe someday...
Good Luck,
--
Boyd Gerber <ger...@zenez.com>
ZENEZ 3748 Valley Forge Road, Magna Utah 84044
Office 801-250-0795 FAX 801-250-7975
Jean-Pierre Radley
|
| I agree totally. I have been fighting with the openssh-3.0p1 with gcc on
| OSR 5.0.6a with all the patches installed. I am using one of the latest
| snapshots of openssl.
I have openssl 0.9.6, gcc 3.0.3, OSR 5.0.6.a; yesterday I downloaded
openssh 3.0p1, ran configure, make, and make install without the least
bit of hacking.
--
JP
Tony Lawrence
Which usually means that you have previously installed something that
the rest of us haven't, and therefore happen to have all the things that
are prerequisites.
And that's the problem with this stuff, with Skunkware, with SCO
products in general: dependencies are very often NOT documented. A
person who discovers, for example, that they need XYZ will very often
find that XYZ, whether obtained as source or binary, will fail
mysteriously. Usually it's just because they need PQR, which in turn
might need ABC, but finding that crap out is difficult at best.
Contrast that with wonderful things like Perl's CPAN module or RedHat's
Update Agent that (usually) just take care of everything for you.
Custom should be half so good..
Bill Vermillion
Or FreeBSD 'ports' system. Best I've seen - never sweat any
dependancies at it takes care of them all.
Bill
Tony Lawrence
But again, let us not forget that there is no perfection. I just tried
to use CPAN on a Red Hat system to upgrade CPAN itself- which should be
a perfectly reasonable thing since the starting screen even suggests
just that.
Total, miserable, break everything failure. It managed to upgrade perl
- almost- but then died whimpering. Had to do it by hand the normal
way, and even then it still seems to be broken..
Roberto Zini
Jean-Pierre,
can you run "ldd" against the binaries to find out the libraries
being used by the programs ?
Thanks,
Roberto
--
---------------------------------------------------------------------
Roberto Zini email : r.z...@strhold.it
Technical Support Manager -- Strhold Evolution Division R.E. (ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)
Jean-Pierre Radley
| Jean-Pierre Radley wrote:
| >
| > Boyd Lynn Gerber propounded (on Tue, Nov 13, 2001 at 04:30:48PM +0000):
| > |
| > | I agree totally. I have been fighting with the openssh-3.0p1 with gcc on
| > | OSR 5.0.6a with all the patches installed. I am using one of the latest
| > | snapshots of openssl.
| >
| > I have openssl 0.9.6, gcc 3.0.3, OSR 5.0.6.a; yesterday I downloaded
| > openssh 3.0p1, ran configure, make, and make install without the least
| > bit of hacking.
|
| being used by the programs ?
Both ssh and sshd use:
/usr/local/lib/libz.so
/usr/lib/libsocket.so.2
/lib/libprot.so.1
/usr/lib/libc.so.1
/usr/lib/libresolv.so.1
--
JP