11–19 of 19 posts
Go/crypto already implements elliptic curve cryptography[1], so I’m curious which specific elliptic curve primitives (or algorithms) they added to their fork.
________
I’m not sure I understand why Protonmail forked the Go crypto library here. Did they fork the entire thing and make substantial changes/updates throughout, or did they just make changes to the PGP implementation available in Go/crypto? Go/crypto already implements elliptic curve cryptography[1], so I’m curious which specific elliptic curve primitives (or algorithms) they added to their fork. ________ 1. https://golan…
https://github.com/golang/crypto/compare/master...ProtonMail...
They changed defaults. 570d0c5fa7ef500786f15958b39af43af3359719 is interesting: "Add secp256k1 / x25519 / brainpool curves to openpgp".
Earlier quoted context omitted.
For those wondering, the license for Sequoia is GPLv3.
So not an option for iOS iPhone email clients?
Earlier quoted context omitted.
Why can't you put GPL v3 software (or Apache or whatever GPL-compatible license you prefer) into the app store?
Not a lawyer, but I assume because the GPL v3 requires that other people be able to modify the program and redistribute their modified versions. Since Apple are the sole gatekeepers of anyone’s ability to distribute iOS apps to users, complying with the license is problematic.
Long story short, the GPL requires you to grant a license to run the application for any purpose. You can also not add additional constraints to this. The App Store's terms and conditions say that you may only offer the software to be used under the usage terms that Apple gives. These two things are in conflict. Apple generally does not approve apps with a GPL license and most people think it's because of this reason (as far as I know they haven't ever made a comment about it). A few apps have apparently made it through, it seems this has been an error on Apple's part.
Earlier quoted context omitted.
So not an option for iOS iPhone email clients?
Why can't you put GPL v3 software (or Apache or whatever GPL-compatible license you prefer) into the app store?
IANAL, but my understanding is GPL means any distribution has to come with source upon reasonable request. Apple doesn't have source and thus can't comply with that, and shouldn't distribute the binaries.
LGPL I believe says that the LGPL portion has to user-replaceable. Seems incompatible with code signing enforcement and static linking.
Now, I think a lot of people are probably breaking the letter and spirit of these licenses and publishing to the app store anyway.
Edit: after googling around, it seems this was a popular conversation topic around 2011, and the part being discussed was mostly Apple's TOS rather than above points about the license.
I wonder if/when a C or C++ bindings to this library will be made. It would be nice to have some alternative to GpgME.
I’m not sure I understand why Protonmail forked the Go crypto library here. Did they fork the entire thing and make substantial changes/updates throughout, or did they just make changes to the PGP implementation available in Go/crypto? Go/crypto already implements elliptic curve cryptography[1], so I’m curious which specific elliptic curve primitives (or algorithms) they added to their fork. ________ 1. https://golan…
https://github.com/golang/go/issues/30141
"We will be deprecating the packages listed above, except openpgp/, otr/ and xts/.
I'll update the proposal and send a CL shortly."
Earlier quoted context omitted.
Why can't you put GPL v3 software (or Apache or whatever GPL-compatible license you prefer) into the app store?
I think GPL at any version would be a problem with the app store. LGPL too. IANAL, but my understanding is GPL means any distribution has to come with source upon reasonable request. Apple doesn't have source and thus can't comply with that, and shouldn't distribute the binaries. LGPL I believe says that the LGPL portion has to user-replaceable. Seems incompatible with code signing enforcement and static linking. Now…