Hi Miroslav,
On Wed, Sep 08, 2021 at 08:02:35PM +0200, Miroslav Zagorac wrote:
> On 09/08/2021 07:57 PM, Miroslav Zagorac wrote:
> > On 09/08/2021 07:42 PM, Willy Tarreau wrote:
> > > No rush on this one, I'll let you think about it, just let me know if we
> > > need to temporarily disable it from
Hi HAProxy Team,
Vanessa from Toptal here! I promise this will be quick. I just read one of
your posts -
https://www.haproxy.com/blog/power-your-consul-service-mesh-with-haproxy/
and I was hoping that we could connect.
I totally agree when you mention that Kubernetes makes configuring a
service m
Hello Jonathan,
On Wed, 8 Sept 2021 at 21:28, Jonathan Greig wrote:
>
> Hello! My name is Jonathan Greig and I'm a reporter for ZDNet. I'm
> writing a story about CVE-2021-40346 and I was wondering if
> Ha Proxy had any comment about the vulnerability.
Just making sure you are aware that this is
Hello! My name is Jonathan Greig and I'm a reporter for ZDNet. I'm writing a
story about CVE-2021-40346 and I was wondering if Ha Proxy had any comment
about the vulnerability.
Thanks,
Jonathan
On Fri, 2021-07-09 at 16:23 -0700, Jacob Champion wrote:
> Hi all,
>
> [Please keep me CC'd on replies, if you would.]
>
> Quick interoperability question, regarding this paragraph in the PROXY
> v2 spec:
Hello,
Just to double-check, is there a better way for me to have asked my
question, or so
On 09/08/2021 07:57 PM, Miroslav Zagorac wrote:
On 09/08/2021 07:42 PM, Willy Tarreau wrote:
No rush on this one, I'll let you think about it, just let me know if we
need to temporarily disable it from the CI, or if you just want a day or
two of checking before knowing if you can get a quick sol
On 09/08/2021 07:42 PM, Willy Tarreau wrote:
No rush on this one, I'll let you think about it, just let me know if we
need to temporarily disable it from the CI, or if you just want a day or
two of checking before knowing if you can get a quick solution or if it
will take more time.
Thank you
On Wed, Sep 08, 2021 at 07:23:59PM +0200, Miroslav Zagorac wrote:
> On 09/08/2021 06:46 PM, Willy Tarreau wrote:
> > I have no doubt about this, what I mean is that once such needs are
> > identified, as much as possible we should try to move these parts into
> > the proper location (vars), or if r
On 09/08/2021 06:46 PM, Willy Tarreau wrote:
I have no doubt about this, what I mean is that once such needs are
identified, as much as possible we should try to move these parts into
the proper location (vars), or if really needed, that must be clearly
explained around the code so that someone e
Willy,
>
> Fred told me that he manages to build it using the fork of openssl that
> contains the proper stuff. Hopefully it should get merged soon. But with
> BoringSSL the problem is that something that works on monday suddenly
> fails to build on tuesday and there's no stable branch so you're
On Wed, Sep 08, 2021 at 06:30:15PM +0200, Miroslav Zagorac wrote:
> there is a reason why i used some functions related to
> reading/setting/searching variables. If I could use the original haproxy
> functions, I wouldn't write these because duplicating the
> code doesn't make sense.
I have no do
On 09/08/2021 04:41 PM, Willy Tarreau wrote:
Hi Miroslav,
I just discovered that the changes I've made to the totally broken
variables API now broke opentracing because apparently it's using
some of the variable code's internals for its own use:
https://github.com/haproxy/haproxy/runs/35454
Hi Miroslav,
I just discovered that the changes I've made to the totally broken
variables API now broke opentracing because apparently it's using
some of the variable code's internals for its own use:
https://github.com/haproxy/haproxy/runs/3545475810
That's annoying because unbreaking the AP
On Wed, Sep 08, 2021 at 12:34:49PM +0200, Aleksandar Lazic wrote:
> On 08.09.21 11:07, Willy Tarreau wrote:
> > On Wed, Sep 08, 2021 at 01:58:00PM +0500, ??? wrote:
> > > ??, 8 . 2021 ?. ? 13:54, Willy Tarreau :
> > >
> > > > On Wed, Sep 08, 2021 at 12:05:23PM +0500, ??? wrot
On 08.09.21 11:07, Willy Tarreau wrote:
On Wed, Sep 08, 2021 at 01:58:00PM +0500, ??? wrote:
??, 8 . 2021 ?. ? 13:54, Willy Tarreau :
On Wed, Sep 08, 2021 at 12:05:23PM +0500, ??? wrote:
Hello, Bob
I tracked an issue https://github.com/haproxy/haproxy/issues/1386
let
On Wed, Sep 08, 2021 at 01:58:00PM +0500, ??? wrote:
> ??, 8 . 2021 ?. ? 13:54, Willy Tarreau :
>
> > On Wed, Sep 08, 2021 at 12:05:23PM +0500, ??? wrote:
> > > Hello, Bob
> > >
> > > I tracked an issue https://github.com/haproxy/haproxy/issues/1386
> > >
> > >
> > > let's t
ср, 8 сент. 2021 г. в 13:54, Willy Tarreau :
> On Wed, Sep 08, 2021 at 12:05:23PM +0500, ??? wrote:
> > Hello, Bob
> >
> > I tracked an issue https://github.com/haproxy/haproxy/issues/1386
> >
> >
> > let's track activity there
>
> Quite frankly, I'm seriously wondering how long we'll wa
On Wed, Sep 08, 2021 at 12:05:23PM +0500, ??? wrote:
> Hello, Bob
>
> I tracked an issue https://github.com/haproxy/haproxy/issues/1386
>
>
> let's track activity there
Quite frankly, I'm seriously wondering how long we'll want to keep
supporting that constantly breaking library. Does
❦ 8 September 2021 09:02 +02, Artur:
> Hello,
>
> Thank you.
>
> Could you please explain the version numbering differences between official
> haproxy release and the linux distributions
> packages ?
>
> For example : 2.4.4 (official) -> 2.4.3-2~bpo10+1 (Debian 10
> backports)
2.4.3-2~bpo10+1
Hello, Bob
I tracked an issue https://github.com/haproxy/haproxy/issues/1386
let's track activity there
вт, 7 сент. 2021 г. в 22:58, Zakharychev, Bob :
> BoringSSL commit dddb60e, "Make most of crypto/x509 opaque.", breaks
> compilation of HAProxy with the following errors (log from compiling
20 matches
Mail list logo
