Re: svn commit: r1863018 - /subversion/trunk/subversion/libsvn_subr/win32_crypto.c

2019-07-14 Thread Branko Čibej
On 14.07.2019 17:51, Evgeny Kotkov wrote: > Branko Čibej writes: > >> Uh. I don't think so. >> >> First of all, the reference to Chromium source is a red herring ... that >> code disables CRL/OCSP checks *if some caller required it to*. You'll >> find that browsers do, indeed, check CRL or OCSP

Re: svn commit: r1863018 - /subversion/trunk/subversion/libsvn_subr/win32_crypto.c

2019-07-14 Thread Evgeny Kotkov
Branko Čibej writes: > Uh. I don't think so. > > First of all, the reference to Chromium source is a red herring ... that > code disables CRL/OCSP checks *if some caller required it to*. You'll > find that browsers do, indeed, check CRL or OCSP info, if it's available. I went through an

Re: svn commit: r1863018 - /subversion/trunk/subversion/libsvn_subr/win32_crypto.c

2019-07-13 Thread Branko Čibej
On 13.07.2019 23:31, kot...@apache.org wrote: > Author: kotkov > Date: Sat Jul 13 21:31:25 2019 > New Revision: 1863018 > > URL: http://svn.apache.org/viewvc?rev=1863018=rev > Log: > Win32: tweak the SSL certificate validation override to avoid hitting the wire > for URL based objects and