Re: [Acme] RFC draft-ietf-acme-acme-02 - tls SNI name

2016-10-14 Thread Ben Irving
On Thu, Oct 13, 2016 at 1:10 PM Alan Doherty wrote: > At 17:39 13/10/2016 Thursday, Ben Irving wrote: > >Hello, > > > >I have ran into a very similar use case. In my case I'm using Haproxy to > route tcp requests based on the server name indication to upstream web > servers where the TLS request

Re: [Acme] RFC draft-ietf-acme-acme-02 - tls SNI name

2016-10-14 Thread Alan Doherty
At 16:31 14/10/2016 Friday, Ben Irving wrote: >On Thu, Oct 13, 2016 at 1:10 PM Alan Doherty ><i...@alandoherty.net> wrote: >At 17:39 13/10/2016Â Thursday, Ben Irving wrote: >>Hello, >> >>I have ran into a very similar use case. In my case I'm using Haproxy to >>ro

Re: [Acme] RFC draft-ietf-acme-acme-02 - tls SNI name

2016-10-14 Thread Ben Irving
On Fri, Oct 14, 2016 at 9:53 AM Alan Doherty wrote: > At 16:31 14/10/2016 Friday, Ben Irving wrote: > > > >On Thu, Oct 13, 2016 at 1:10 PM Alan Doherty < i...@alandoherty.net>i...@alandoherty.net> wrote: > >At 17:39 13/10/2016Â Thursday, Ben Irving wrote: > >>Hello, > >> > >>I have ran into a v

Re: [Acme] RFC draft-ietf-acme-acme-02 - tls SNI name

2016-10-14 Thread Ilari Liusvaara
On Fri, Oct 14, 2016 at 05:07:22PM +, Ben Irving wrote: > On Fri, Oct 14, 2016 at 9:53 AM Alan Doherty wrote: > > > > btw in http-01 the acme client can specify to the server whether to use > > http://www.domain1.com/.well-known/acme-challenge/ > > or https://www.domain1.com/.well-known/acme-c

Re: [Acme] RFC draft-ietf-acme-acme-02 - tls SNI name

2016-10-14 Thread Patrick Figel
On 14/10/16 18:53, Alan Doherty wrote: > btw in http-01 the acme client can specify to the server whether to > use http://www.domain1.com/.well-known/acme-challenge/ or > https://www.domain1.com/.well-known/acme-challenge/ directly > > "The client’s response to this challenge indicates whether i