Does anyone know of a way to avoid the automatic CWD command in libCurl,
as I am connecting to an FTP server that indicates "\" is current working
directory. I am only uploading files to this server, so I do not need to
know the current working directory.
This is a very old windows based embedde
On Tue, 10 Feb 2015, Daniel Stenberg wrote:
> > I was wondering should I be using HAVE_BORINGSSL or
> > OPENSSL_IS_BORINGSSL in some of my pre-processor checks -
> > or doesn't that matter?
>
> That's not a big difference in reality:
Cheers for the clarification Daniel - much appreciated.
> -
On Tue, 10 Feb 2015, Alessandro Ghedini wrote:
> > Over the weekend I came to build curl on Centos and found that it
> > didn't build against the build in version of OpenSSL (v0.9.8b) :(
> >
> > I appreciate this is a fairly old version but given we support 0.9.7+
> > (according to our docs) I d
On Mon, 9 Feb 2015, Isaac Boukris wrote:
> > From my knowledge in this area that doesn't seem quite right and if we
> > can save an extra round trip, and it is valid to do so, then great ;-)
>
> It works well in my tests and according to RFC 4559 (SPNEGO) it should be
> perfectly valid.
It seems
On Mon, 9 Feb 2015, Steve Holme wrote:
I was wondering should I be using HAVE_BORINGSSL or OPENSSL_IS_BORINGSSL in
some of my pre-processor checks - or doesn't that matter?
That's not a big difference in reality:
- OPENSSL_IS_BORINGSSL is defined in the boringssl headers
- HAVE_BORINGSSL is
On Mon, Feb 09, 2015 at 09:18:21PM +, Steve Holme wrote:
> On Mon, 9 Feb 2015, GitHub wrote:
>
> > openssl: Disable OCSP in old versions of OpenSSL
> >
> > Versions of OpenSSL prior to v0.9.8h do not support the necessary
> > functions for OCSP stapling.
>
> As most of you know... I am pred