Replies: 1 comment 1 reply
-
Hey 👋 As a disclaimer, I'm not a lawyer, but:
I'm not sure I understand why not -
We considered it, and I wouldn't be opposed to it, but this would essentially require us to receive permission to do so from all copyright holders, i.e. all authors of OpenPGP.js and the code it was based on, such as the gpg4browsers code mentioned in the issue you linked. So I think it's probably not feasible.
Not specifically; I would recommend interfacing with an implementation in another language, in that case. For example, you could use gopenpgp via the command line interface gosop. |
Beta Was this translation helpful? Give feedback.
-
Hi there! I'm working on some key/signature verification in Kibana and was hoping to use
openpgpjs
as we're already generating the signatures in question elsewhere using https://github.com/ProtonMail/gopenpgp. The problem, however, is thatopenpgpjs
is licensed under LGPLv3, and I don't think we can suitably adhere to the terms of this license in a Node.js environment.For example, we can't allow users to easily provide a modified or "interface compatible" version of
openpgpjs
in a Node environment, because we can't load it as a separate script file like we might be able to in a browser environment. See #1427 for relevant discussion around Webpack/client-side JS.Digging through issues, I see #10 from 2011. I'm curious if the thoughts around licensing have potentially shifted here, and if it'd be possible to discuss dual licensing the project under a more permissive license like MIT. If not, I'd be eager to hear if there is a recommended alternative implementation of PGP in Node.
A few related discussions
Thanks much!
Beta Was this translation helpful? Give feedback.
All reactions