We saw weird behaviours when mixing in our application openssl 1.0.0 and using Security.framework/TokenD. Using stock openssl resolved this.
Raul On Apr 16, 2013, at 3:43 PM, Peter Hartmann <[email protected]> wrote: > On 04/16/2013 01:19 PM, Richard Moore wrote: >> 2) We could say 1.0.0 is the minimum. > > +1 > > This is the de-facto standard already anyhow, at least for me; i.e. I > have been acting like "if it works on my PC (1.0.x) and goes through CI > (apparently 1.0.x) it is good enough". > So I am all for noting this down somewhere: 1.0.x is guaranteed to work > and fixes for 0.9.x are welcome (just like fixes for the configure > option -openssl-linked, which I think is not tested anywhere either). > > Peter > > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from your > system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
