Greetings OpenSSH developers, wolfSSL now has a stable port for any interested we are nearly ready to submit a pull request to openssh-portable repository. For any and all interested we are ready for some alpha testing. Testing should be as easy as doing the following steps: git clone https://github.com/kaleb-himes/openssh-portable.git git clone https://github.com/kaleb-himes/wolfssl.git cd wolfssl ./autogen.sh ./configure --prefix=/usr/local/lib --enable-openssh && make && sudo make install cd .. cd openssh-portable autoreconf ./configure --with-wolfssl=/usr/local/lib --with-pam && make && make tests Our Jenkins server is now using this port to actively checkout changes from github and is also running all slave nodes using SSH with this port. This provides us with some real-world testing in addition to the unit tests. We would ask for any feedback on our port from the openSSH community and welcome any questions before we submit a pull request to you in the near future. Thank you all for your time and consideration in this matter, we look forward to hearing from you. Our sincerest Regards, The wolfSSL Team and Kaleb Himes www.wolfssl.com kaleb at wolfssl.com Skype: kaleb.himes +1 406 381 9556
On 28 Dec 2015, at 18:32, Kaleb Himes <kaleb at wolfssl.com> wrote:> wolfSSL now has a stable port for any interested we are nearly ready to > submit a pull request to openssh-portable repository. > > For any and all interested we are ready for some alpha testing.Just to help me planning the use & dissemination of this. 1) Fair to assume that you would expect (user and) distributor of a (binary or source) distribution of an openssh+wolfssl (As opposed to an openssh+openssl) to have agreed to BOTH the: a) the OpenSSH license -and- b) the GPL (or a commercial license entered into with WolfSSL) ? and that (at least) the GPL covers the entire derived work ? (the OpenSSH license does not). 2) And secondly (- are you, as the authors, all -) offering these OpenSSL modifications (i.e. the ?patch) to the world (or to OpenSSL) as part of the work ? Or do you see the patch itself as something purely for OpenSSL; sufficiently free of entanglement to be redistributed solely under the OpenSSH license agreement ? Thanks, Dw.