OpenSSH port question

[Rip Loomis]

Andy--
This should be in an FAQ somewhere, but here's
a quick summary of the situation:

1.  OpenSSH ("basic") is principally maintained
	by the OpenBSD developers.  Relevant
	fixes from the portable version *may*
	be incorporated if they are applicable
	to OpenBSD, but there is a specific
	intent to keep the OpenBSD version
	clean of the #ifdefs that make the
	ssh.com 1.2.x code so troublesome
	to follow/audit.

2.  The OpenSSH Portability Team has taken
	the "clean" OpenBSD implementation
	and modified it as required to allow
	compilation and support on other
	platforms.  Again, there is a specific
	interest in keeping the diffs clean
	and minimal, but there are obviously
	changes that need to be incorporated.
	Damien Miller and other folks in the
	portability team communicate with the
	upstream (essentially OpenBSD)
	developers to keep things in sync.

3.  OpenSSH has already been ported to
	NeXT and CygWin (Win32 + Cygnus
	support libraries), so I think that what
	you want to do is possible.  Not
	sure whether the CygWin port might
	already include terminal emulation--
	I use PuTTY as my Win32 client.

Bottom line--I would recommend that you submit
your patches to Damien via the list.  That's what
seems to be working for other folks right now.
Obviously, if you've got 100K of code, it might
be better to put it up for download and send a
pointer.

Hope this helps--

Rip Loomis		Voice Number: (410) 953-6874
--------------------------------------------------------
Senior Systems Security Engineer
Center for Information Security Technology
Science Applications International Corporation
http://www.cist.saic.com


-----Original Message-----
From: Andrew Zabolotny [mailto:bit at eltech.ru]
Sent: Wednesday, August 30, 2000 4:34 AM
To: openssh-unix-dev-list at mindrot.org
Subject: OpenSSH port question


Good day!

A little time ago I have ported the "original" ssh 1.2.30 to OS/2.
Unfortunately, I was mislead by the gnu-COPYING-GPL file that is present in
the
ssh root dir, thus was under impression that ssh is GPL as well. I was
shaken
when I have discovered my mistake :-) This basically made it unusable for
many
users which want to use ssh in commercial environments.

Thus I decided to port OpenSSH to OS/2, to get a really free ssh. After
looking
at your web site I've found that there are two flavours of openssh: OpenBSD
and
"portable" version. Thus I have the question: which flavour should I base my
work upon? I could derive it from "portable" ssh, but I believe I will find
hardly a single common line between other OS-es and OS/2.

In general, I prefer to avoid all kinds of ugly #ifdef's spread across the
code. They make sense only for code which is shared by more than one
platform;
for OS/2-specific code I'm going to write several additional modules, as I
did
for original ssh/sshd. This includes a terminal emulator (um... maybe it
would
be helpful for other platforms as well which don't have "built-in"
terminals),
a file-system path translator (which maps all kinds of "/etc" and "/dev")
and a
misc module for the rest of compatibility stuff.

I'm a little worried by the two flavours being developed at the same time.
How
you "refresh" the "base" of the openssh in the "portable" version? Having
two
separate versions forces to synchronize these two version often, who's in
charge for this?

Ok, I'll stop here for now.

Greetings,
    _\ndy at teamOS/2