3 ms·

Howdy, I'm OP! Neat to see an old blog post on HN. 1) GPL/LGPL are not incompatible with iOS, they are incompatible with the App Store. I don't care about th

by mrmekon 14y ago

Howdy, I'm OP! Neat to see an old blog post on HN. 1) GPL/LGPL are not incompatible with iOS, they are incompatible with the App Store. I don't care about that. I was writing a GPL'd app, and I would be pleased with a GPL'd library. iOS was also not my only target. (response to one of your other posts) 2) The idea of 'what's enough' was for e-mail decryption only. Which is what I wanted to do. And I wrote an open-source OpenPGP library to do it: https://github.com/mrmekon/libsimplepgp https://github.com/mrmekon/libsimplepgp 3) I don't need 'some library to solve encryption and decryption', I need 'some library to solve decryption of PGP-encrypted emails.' A partial implementation of OpenPGP, as a library. Other crypto packages don't support the OpenPGP packet format. 4) Read section 4, "Packet Syntax", the entire concept behind the OpenPGP format: http://www.ietf.org/rfc/rfc2440.txt http://www.ietf.org/rfc/rfc2440.txt

acqq 14y ago
Wow, it's really nice that you did make a library that solves exactly the problem you've had. IMHO you are really a very specific case, producing GPL iOS code which certainly can't go in the App store. Updating your blog post with the link to your library would make the post much more relevant, weren't you able to do so? I understood you "message splitting" like the plaintext or the ciphertext being split, which as far as I know neither is. RFC does use "packets" packets to denote segments as the "packet" with the key and the "packet" with the cypertext but I don't consider recognizing where which begins in order to process it is "splitting." I see now what you wanted to say. Re "other crypto packages don't support the OpenPGP packet format" -- I understood that libgcrypt also doesn't, so wouldn't be more in the spirit of your goal (if it is) to have OpenPGP more widely used to base libsimplepgp on some BSD, Apache or similarly licensed crypto libarary?

by mrmekon 14y ago

acqq 14y ago

Wow, it's really nice that you did make a library that solves exactly the problem you've had. IMHO you are really a very specific case, producing GPL iOS code which certainly can't go in the App store. Updating your blog post with the link to your library would make the post much more relevant, weren't you able to do so? I understood you "message splitting" like the plaintext or the ciphertext being split, which as far as I know neither is. RFC does use "packets" packets to denote segments as the "packet" with the key and the "packet" with the cypertext but I don't consider recognizing where which begins in order to process it is "splitting." I see now what you wanted to say. Re "other crypto packages don't support the OpenPGP packet format" -- I understood that libgcrypt also doesn't, so wouldn't be more in the spirit of your goal (if it is) to have OpenPGP more widely used to base libsimplepgp on some BSD, Apache or similarly licensed crypto libarary?