savannah-register-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #14426] Submission of TUServer


From: William Lupshenko
Subject: [Savannah-register-public] [task #14426] Submission of TUServer
Date: Thu, 30 Mar 2017 02:24:15 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #6, task #14426 (project administration):

Following https://github.com/nodejs/node/wiki/OpenSSL-upgrade-process, NodeJS
uses SSL for SSL features (https://nodejs.org/api/tls.html), HTTPS
(https://nodejs.org/api/https.html), but also it uses SSL for crypto
(https://nodejs.org/api/crypto.html) that my program use, but, it does that by
calling a MIT licensed JavaScript code that uses bindings to C++ functions
(also MIT) that communicate with OpenSSL
(https://github.com/Lupshenko/TUServer/blob/master/main.js)
(https://github.com/nodejs/node/blob/master/lib/crypto.js)
(https://github.com/nodejs/node/blob/master/src/node_crypto.cc)
(https://github.com/nodejs/node/blob/master/src/tls_wrap.cc). I'm not sure,
but I think that this non direct communication doesn't violate the license. Am
I right?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?14426>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]