Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPL and RSA-MD license conflict #218

Open
sorenstoutner opened this issue Nov 18, 2024 · 3 comments
Open

GPL and RSA-MD license conflict #218

sorenstoutner opened this issue Nov 18, 2024 · 3 comments

Comments

@sorenstoutner
Copy link

sorenstoutner commented Nov 18, 2024

We're getting really close to having Feather Wallet ready for inclusion in Debian, but we ran up against a license conflict.

src/qrcode/QrCode.cpp
src/qrcode/QrCode.h
src/qrcode/QrCode_p.h
src/utils/AsyncTask.h

are licensed under the GPL.

monero/contrib/epee/include/md5_l.h
monero/contrib/epee/include/md5_l.inl

are licensed under a combination of BDS-3-clause and RSA-MD.

https://github.com/feather-wallet/monero/blob/84d813f5ee54d269f1ced8f495924e00fc40bb0d/contrib/epee/include/md5_l.inl#L33-L58

The RSA-MD, sometimes known as the RSA-MD5, is incompatible with the GPL.

This is obviously not only a problem in Debian, but for any distribution of the Feather Wallet binary. Before looking into it more deeply, do you as upstream have an indication as to be the best way to resolve the conflict?

@sorenstoutner
Copy link
Author

I am not certain how important epee is to Feather Wallet, or if any of its code even gets compiled into the feather binary. I did confirm that if these files aren't present Feather Wallet doesn't build, but that doesn't automatically mean any of their object code is used. I haven't yet spent the time to see how easy it would be to excise or replace this code. Brief searches on the internet indicate that there are replacements for these two RSA-MD files that some projects use, possibly as drop-in replacements. Also, there is some indication that, in response to licensing compatibility concerns, upstream relicensed some of these files into something akin to the public domain. But several of the links relating to relicensing issues are dead, and I haven't done enough research to know if specific code that was included in these files was relicensed.

@bgermann
Copy link

Please see dinhvh/libetpan#450 for a possible fix.

@bgermann
Copy link

The fix is not usable as-is because Monero has changed the code to be namespaced in C++.
I have filed a different solution upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants