Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: Openssh 4.2p1 and Openssh3.6.1 compatibility

Subject: Re: Openssh 4.2p1 and Openssh3.6.1 compatibility
Date: Thu, 15 Dec 2005 12:35:23 +1100
On Tue, Dec 13, 2005 at 03:30:06PM +0100, Aidan Mcgrath L (AT/LMI) wrote:

we recently were requested to upgrade our Openssh to the latest version
which was SMCossh421 This caused a problem with some Applications in
the system. I recently received a mail to this effect i.e...

"we have concluded that ... is not compatible with this version of
Open SSH. The reason being, SFTP client of ... uses an option -b of sftp
command for batch file processing. This option has been removed in openssh
4.1. In the absence of this option, SFTP client would not be able to
work properly in the system.  We therefore suggests that openssh 3.6.1
p1 should additionally be included in the System as ... is dependent on
it. I suppose the package names of 3.6.1 and 4.1 are different so they
can co exist in the system. "

1) Is this correct?

No (at least, not for the main distribution. It's possible that the
creator of the binary package changed something, you would have to
ask them.)  sftp's -b option is present in the source for 4.1p1 and 4.2p1.

2) Is it also true that 4.2p1 version has not got this (batch handling)
option, and is therefore not backward compatible to 3.6.1, and

No.

if so:
3) Can the two versions, 3.6.1 and 4.2p1, coexist on the same system.

Yes, as long as they're compiled to use different paths for their binaries
(again, ask the creator of your packages, or build them yourself giving
different "--prefix" paths to configure).

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

<Prev in Thread] Current Thread [Next in Thread>