Hooray! Got at least mostly complete LibreSSL and WolfSSL installed on MacOS to integrate in some projects. Mostly for hashing, but it's nice to have them available. Need to work out why my WolfSSL is throwing build-time errors on DragonFly BSD though...
Not a fan of WolfSSL's GPLv2 license, but I like it being a small, embeddable crypto lib. Might have to see if there's a more permissive alternative with similar options (mostly things like SHA3, BLAKE2/SHAKE2, Whirlpool, and Serpent)
@architect Does the GPLv2 licence in this case limit where you could use it?
@_emacsomancer
Not for work, since the result wouldn't be distributed outside of my team, but possibly for my personal uses. I'd have to review the restrictions of GPLv2 to be sure, but I'm also just more comfortable with permissive licensesin general.
@architect Though generally I'm not a great fan of non-reciprocal licences, I'll admit that for libraries like SSL's, it probably does make more sense to license them with a non-reciprocal licence.
@_emacsomancer
I think the reciprocation is good, and is in everyone's best interests, I'm just not fond of the compulsory approach, or the virality of the GPL. I know people aren't perfect, but I'd rather people contribute back because it benefits them as well, than have them bound by a license to do so.
@architect I would like to live in the world where a BSD-style licence was appropriate, but I'm not convinced that we do.
The GPL is pretty reasonable: "Here is some code that you can use, modify, and distribute. You just can't take those rights away from anyone else." Of course, webservices render it rather toothless in many cases. (The AGPL perhaps addresses this better.)
@_emacsomancer @architect BSD license was designed for academics to keep work in the open and then close it up and turn proprietary after graduation. It works well for that.
