literal 2.9-dev8 tag. Will rebuild with the latest
master, to include commit e7bae7a. Thank you!
Valters Jansons
drama. The rebuilt binary has behaved stable -- thank
you for bringing attention to the flag.
Overall, feels strange, but doesn't seem like there is anything
actionable here in the end.
Thank you in any case!
Valters Jansons
are not related -- instead
being caused by some clients potentially connecting to port 443 and
trying to talk plaintext, or wanting to run TLS 1.1 or older.
Let me know if I can provide any more insights.
Best regards
Valters Jansons
ing
"unexpected" but HAProxy believes it did. Is this something that you
have ideas about, or if that's something that gets dealt with in a
separate patch?
Best regards,
Valters Jansons
o
it. But the H2 spec says the exchange is successful, and the observed
half-close is okay.
Best regards,
Valters Jansons
REAMs, so this should
not be a major issue, but something still feels strange here with
connection state processing.
Let me know if I can help brainstorm this further.
Best regards,
Valters Jansons
ssue with.
Hopefully having a sample application locally makes it easier for you
to look at the raw traffic, and trace HAProxy itself.
Please let me know if I can help out in any other way!
Best regards,
Valters Jansons
): leaving :
h2c=0x560dddb99c50(B,FRH) h2s=0x560dddb064a0(1,HCR)
---
Best regards,
Valters Jansons
frontend fe
bind 127.0.0.1:80 proto h2
default_backend be
backend be
server srv 65.109.88.38:12790 proto h2
---
Best regards,
Valters Jansons
mething that you can expect to hold up in
the long run, and it's not something construction folks would advise.
So just patch/update your vulnerable applications; and where vendors
provide mitigation steps - apply those instead.
--
Valters Jansons
On Tue, Jul 20, 2021 at 9:49 AM Lukas Tribus wrote:
> It's secur...@haproxy.org, it's somehow well hidden in doc/intro.txt
> (that is the *starter* guide).
>
> I would definitely suggest putting it on the website haproxy.org, and
> in the repository move it to a different file, like MAINTAINERS.
On Tue, Jun 8, 2021 at 10:01 AM Willy Tarreau wrote:
> On Mon, Jun 07, 2021 at 12:58:22PM +0500, ??? wrote:
> > ??, 7 ???. 2021 ?. ? 12:20, Valters Jansons :
> > > On Mon, Jun 7, 2021 at 12:34 AM Ismail Azerty
> > > wrote:
> > > > For some se
On Mon, Jun 7, 2021 at 12:34 AM Ismail Azerty wrote:
> For some security reasons, our security teams want us to use the
> official repository, or recompile the whole project on ubuntu 20.
Official Ubuntu repositories are "slow" to update due to LTS policies,
ensuring no potentially
Hello everyone,
There is a global parameter for SSL session cache block count
(tune.ssl.cachesize). Documentation for it currently states: A block
uses approximately 200 bytes of memory.
This estimate of 200B for each block has been there since version 1.5,
and it does not seem to align with
bd0ff63f072 for haproxy-2.0 trees, expectedly
shipping as v2.1.1 and v2.0.11 respectively.
Big thank you to Christopher for the work done!
Best regards,
Valters Jansons
regards,
Valters Jansons
16 matches
Mail list logo
