OpenSSH ports and crypto issues

[mouring at etoh.eviladmin.org]

On Fri, 25 May 2001, Amol Deshpande wrote:

> hi,
>
> I am working on a windows NT version of openssh. It's mostly working
> (ssh.exe, ssh-keygen.exe to be precise), except for some minor UI issues.
> however, i have a couple of questions about making the port available:
>
> 1. minor issue: My port is based on the openbsd ssh source (2.5.2). Is
> this acceptable, or should I base it on the portable source ? I think I
> know the answer to that one. If someone wants to take my diffs against
> base and integrate them into portable, that would be awesome, since I
> won't be able to get around to it for a while.
>

If your looking to get into the portable tree.  You need to provide
patches based on the most recent CVS snapshot from directhit.

> 2. minor issue 2: I am currently using 2 files from a GPLed program in my
> port. It will take some work to remove them, but I can do so if it's not
> desirable to have GPLed source in an OpenSSH port.
>

Depending on what those GPL functions are you may want to look at the
OpenBSD CVS tree for it's equiv (if there is one).

> 3. THE major issue: How do I distribute this ? send diffs to the portable
> distribution maintainer(s) ? Since I live in the U.S, I obviously cannot
> make it available myself. My diffs would consist of diffs from the main
> source, makefiles and a library that implements compatibility routines for
> NT.
>
I believe we are still working under the assumption that changes can
occur to OpenSSH as long as they do not deal with the encryption aspect
of the code.

However, under the new laws (I've not had a chance to read them) this
restriction could be lifted in the future.


My only concern is how you ported it NT, and we currently trying to keep
the differences between OpenBSD and portable down to a managable amount.

- Ben