cURL / Mailing Lists / curl-library / Single Mail


[PATCH] lib/nonblock.c /Amiga/

From: Norbert Kett via curl-library <>
Date: Fri, 27 Nov 2015 12:26:24 +0000 (UTC)

i found a missing & symbol in nonblock.s for amiga. this causes longword read from address 0x1
code:  /* Amiga */  long flags = nonblock ? 1L : 0L;  return IoctlSocket(sockfd, FIONBIO, flags); 
fix:  /* Amiga */  long flags = nonblock ? 1L : 0L;  return IoctlSocket(sockfd, FIONBIO, (char*)&flags); 

 Norbert Kett
Lead Programmer4Flash Interactivephone: +36202500441

      From: "" <>
 Sent: Friday, November 27, 2015 12:00 PM
 Subject: curl-library Digest, Vol 123, Issue 27
Send curl-library mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of curl-library digest..."

Today's Topics:

  1. Re: [PATCH] openssl: allow partial trust chains (Tim Ruehsen)
  2. Re: cUrl and TFO (Daniel Stenberg)


Message: 1
Date: Thu, 26 Nov 2015 12:02:15 +0100
From: Tim Ruehsen <>
Subject: Re: [PATCH] openssl: allow partial trust chains
Message-ID: <9056326.x8TXQTbgu9_at_blitz-lx>
Content-Type: text/plain; charset="us-ascii"

On Thursday 26 November 2015 10:43:07 Petr Pisar wrote:
> On Thu, Nov 26, 2015 at 10:25:31AM +0100, Tim Ruehsen wrote:
> > > If only an intermediate CA in the chain is trusted, setting this
> > > flag also allows the connection when the root CA is not trusted.
> >
> > Maybe I don't get your point.
> > The server cert is signed by an intermediate CA. This is signed by
> > (intermediate cert | root CA). Repeat the last step until you reach the
> > root CA.
> > The root CA is the only one you trust by definition (normally/often root
> > CAs are installed by your distribution).
> I must disagree. For example, many authorities (as a company) have one root
> authority and then several subordinated authorities with different policies.
> For example, one is compliant to government requirements, while the other
> one issues cheaper certificates with less detailed validation. Then I want
> to trust only certificates issued by the one intermediate authority. Adding
> the one subauthority to trusted set and removing the root certificate from
> the set solves the issue for me. Especially when common TLS libraries
> cannot discriminate on certificate policy OIDs.

I just don't like this behavior being the default.
I have nothing against some kind of configuration / option.



Message: 2
Date: Thu, 26 Nov 2015 17:03:32 +0100 (CET)
From: Daniel Stenberg <>
To: libcurl development <>
Subject: Re: cUrl and TFO
Message-ID: <>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Wed, 25 Nov 2015, Inca R wrote:

> I add to the Cc Peeyush. He is the contributor of TFO for Netty and Nghttp2
> and he is the guy actually working on the TFO cUrl implementation.
> We will love to contribute TFO for cUrl and we need all the help you can
> provide to make it happens.


Anything in particular you're looking for right now or stands in the way that
I can help you with?

> We would love to contribute to your best practice document.

You can get the latest version from github here:

I welcome suggestions by email - to me or the http wg mailing list - or as
pull-requests on github. My plan is to submit a -01 version of the draft
within shortly.

Subject: Digest Footer
curl-library mailing list
End of curl-library Digest, Vol 123, Issue 27

List admin:
Received on 2015-11-27