On 2020/01/11 18:23, Jeremie Courreges-Anglas wrote:
> > Great, this change is definitely safe (in fact this header is required
> > by the OCSP RFCs - both the current RFC 6960 and the original 2560).
> >
> > I'll reinclude the diff so it applies with patch (spaces/tabs issue)
> > and CC a couple
On Sat, Jan 11 2020, Stuart Henderson wrote:
> On 2020/01/11 12:48, Kor son of Rynar wrote:
>> Hi Stuart,
>>
>> thank you for your fast reply.
>>
>> On Fri, Jan 10, 2020 at 7:22 PM Stuart Henderson
>> wrote:
>>
>> > On 2020/01/10 19:13, Kor son of Rynar wrote:
>> > > On Fri, Jan 10, 2020 at
On 2020/01/11 12:48, Kor son of Rynar wrote:
> Hi Stuart,
>
> thank you for your fast reply.
>
> On Fri, Jan 10, 2020 at 7:22 PM Stuart Henderson
> wrote:
>
> > On 2020/01/10 19:13, Kor son of Rynar wrote:
> > > On Fri, Jan 10, 2020 at 6:48 PM Kor son of Rynar <
> > daharmaster...@gmail.com>
>
Hi Stuart,
thank you for your fast reply.
On Fri, Jan 10, 2020 at 7:22 PM Stuart Henderson
wrote:
> On 2020/01/10 19:13, Kor son of Rynar wrote:
> > On Fri, Jan 10, 2020 at 6:48 PM Kor son of Rynar <
> daharmaster...@gmail.com>
> > wrote:
> >
> > > >Fix:
> > > Unknown. Could be
On 2020/01/10 19:13, Kor son of Rynar wrote:
> On Fri, Jan 10, 2020 at 6:48 PM Kor son of Rynar
> wrote:
>
> > >Fix:
> > Unknown. Could be related to the lack of "Connection: close"
> > and/or "Content-Type" headers in the HTTP request?
> >
>
> Adding the missing headers seems to
On Fri, Jan 10, 2020 at 6:48 PM Kor son of Rynar
wrote:
> >Fix:
> Unknown. Could be related to the lack of "Connection: close"
> and/or "Content-Type" headers in the HTTP request?
>
Adding the missing headers seems to solve the problem:
--- http.c.orig Fri Jun 28 13:32:49 2019
+++
>Synopsis: ocspcheck fails to load OCSP response from ocsp.sectigo.com
>Category: system amd64
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6-current (GENERIC) #574: Fri Jan 10
10:38:49 MST 2020
dera...@amd64.openbsd.
