Questions on ssh

I am new to SCO as of 6 months ago, but am picking up fast. I consider myself somewhat fluent to SCO but am having troubles on one particular issue. I help support a number of sites with SCO 5.0.5/6/7 I was not aware at the time that 5.0.7 included SSH during install and thus I automatically installed the package I had ftp'd to the machine. I have never been able to get SSH to connect between this SCO 5.0.7 machine and a RH4 machine. I know that the 5.0.7 included SSH version is called from sd and seems to use a different # generator other than the prngd I installed with my version. The SSH I installed on top of the current one would be called from /usr/local/sbin/sshd rather than the /usr/bin/sd sshd....

My question is this:

When I learned that 5.0.7 already had SSH installed, I immediately uninstalled MY version. Would this have deleted any files that the included version needed? What do I need to do to restore/reinstall the included version? I am not sure what version was originally installed with 5.0.7 but if I redownloded that version from an ftp site would it restore exactly as it was installed with SCO?

I just remoted into another site and the 3 packages I normally use for SSH installes are:
OpenSSH 3.1p1
prngd 0.9.23
zlib 1.1.4

More Articles by tporter

Click here to add your comments




Wed Oct 8 11:53:36 2008: Subject:   TonyLawrence


Yeah, I'd guess that is your problem, but it should be easy to fix.

Put your original SCO CD in the drive and run "custom". Drill down into the Openserver software to the "Connectivity" section to find ssh. Reinstall it. I expect that should fix things up.

I'd also uninstall and reinstall the 5.0.7 patch supplements - I don't know for sure that ssh components are involved but I expect that they are.



Wed Oct 8 15:27:23 2008: Subject:   BigDumbDinosaur
http://bcstechnology.net

I have never been able to get SSH to connect between this SCO 5.0.7 machine and a RH4 machine.

Do both machines agree on the port being used to communicate? Port 22 is the default, but not necessarily what was configured at one end. I routinely set up the systems I maintain to ssh on an alternate (dynamic) port, both to discourage dictionary attacks and to protect the system in case a buffer overrun or similar results in the attacker somehow getting in without authentication. If ssh is listening on a dynamic port privilege escalation is more difficult to achieve.

Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments

If you want a picture to show with your comment, go get a Gravatar

Take Control of Your iPhone Apps

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.