As I use components I will update wiki (and not for altruistic reasons -
for
myself so I have it in one place :) and provide examples in c++ (someone
may
later rewrite them in delphi, I don't care about it).
That's perfect for me. Let me know you login name and I'll grant you access.
Any info
> Most likely that's wrong, as I recall the vulnerability,
> it's probably only safe to not enable option
> "SslOpt_ALLOW_UNSAFE_LEGACY_RENEGOTIATION".
I never even meant to enable this option. If it fails I don't care.
Many servers will be upgraded quickly to fix this issue anyway so I don't
thin
Arno Garrels wrote:
> Zvone wrote:
>> well, that's great news i thought it was not fixed already and it was
>> still disabled in "N" version as well. good to know!
>>
>> but what does this mean "require the extension as needed"?
>>
>> if i understood correctly - if you have 098n and server suppor
Zvone wrote:
> well, that's great news i thought it was not fixed already and it was
> still disabled in "N" version as well. good to know!
>
> but what does this mean "require the extension as needed"?
>
> if i understood correctly - if you have 098n and server supports the
> extension, it will
well, that's great news i thought it was not fixed already and it was still
disabled in "N" version as well. good to know!
but what does this mean "require the extension as needed"?
if i understood correctly - if you have 098n and server supports the
extension, it will be used with no additional
Hi,
In OSSL v0.9.8L and v0.9.8m renegotiation support was disabled due to
vulnerability of the SSL protocol. In v0.9.8n renegotiation support was
re-enabled and RFC5746 implemented but require the extension as needed. It's
also possible to enable unsafe legacy renegotiation explicitly by settin
