Is there a way to detect when the SSL library has renegotiation disabled? (Either at compile-time or runtime, although
runtimewould definitely be better because we’ll change our behavior if/when the user updates their SSL library.)
If so, we could skip renegotiation when it’s disabled in the library, but otherwise perform renegotiation like we
normallydo (every 512 MB, I think it is).
Also, the official OpenSSL patch provides a way for the application to re-enable renegotiation. I don’t think all
implementationswill do so, though (e.g., some vendors might have patched it differently).
- Chris