On Thu, Sep 02, 2010, Victor Duchovni wrote: > > It is my impression that enabling tls extensions breaks binary > compatibility, so I cannot replace a "no-tlsext" shared library with > one that support extensions without re-compiling all the clients. So, > some legacy systems still get "no-tlsext" libraries until we move > everyone to 1.0.0. >
A few fields are appended to some structures to support TLS extensions which means that some structures increase in size. These structures are only ever allocated and freed by library calls so binary compatibility *should* be maintained. However there is a slight risk that a highly broken application will allocate the structures itself and poke around in internals to set them up. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected]
