[Development] Gotcha for the IOS port

[Thiago Macieira]

On quinta-feira, 10 de janeiro de 2013 21.20.51, Richard Moore wrote:
> Hi,
> 
> I've not managed to catch the right people on IRC, but one thing to
> watch with the IOS port is that it doesn't ship openssl (which has
> been deprecated on macos for a while). This means that one of the
> following will need to be done:
> 
> 1) qt could include it
> 2) qt apps could ship it themselves
> 3) adding support for the macos/ios crypto library
> 
> Option 1 is tricky legally. Option 2 would mean that apps would be
> bigger. Option 3 is a lot of work, but might be needed for macos
> anyway in future when apple finally remove the ancient version of
> openssl they ship now.

Let's exclude option 1. Adding crypto code to Qt would raise all sorts of 
problems for customers. It's already tricky enough when we're doing wrapper 
around other people's crypto code.

Option 2 is what we have right now.

So it only leaves investigation about option 3. It sounds like we need a 
research project to verify whether their crypto library suffices for our needs. 
After that, we can look into whether it's worth the project to add the other 
backend. (if we do that, we might as well apply Rule of Three and do a third 
backend too, which would be GnuTLS or NSS)

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130110/4951a270/attachment.sig>