OpenSSH ports and crypto issues

[Amol Deshpande]

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.

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.

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. 

 The only part of my source that uses any cryptography is a function
that calls a Crypto Provider DLL to generate a random number (I'm trying
to approximae arc4_random() by using a system provider). Since this DLL
provider is distributed in the system, I don't see a problem with
re-distributing code that uses it. Is that a reasonable assumption w.r.t
export restrictions ?
(I don't think generating a random number involves encryption, but I have
!clue about such things.)


I'd very much like to make this available without treading on anyone's
GPLed toes or having the NSA hunt me down, so please let me know what the
best route to proceed would be.



thanks,
-amol