On Wed, Aug 14, 2019 at 12:52:00AM +0200, Cyril Bonté wrote:
> And I confirm that commit 5b06cb33eb (BUG/MEDIUM: mux_h1: Don't bother
> subscribing in recv if we're not connected) fixes the issue ;-)
Great, thanks for confirming (and for reporting the issue in the first
place)!
Willy
Hi again,
Le 13/08/2019 à 11:57, Willy Tarreau a écrit :
On Tue, Aug 13, 2019 at 11:49:20AM +0200, Willy Tarreau wrote:
Excellent, I think you caught it! I can reproduce it here, except that
it doesn't last long, as soon as I get the socket error it's done. So
we indeed broke something in the
Hi Aleks,
On Tue, Aug 13, 2019 at 07:02:49PM +, Aleksandar Lazic wrote:
> Have anyone seen this and maybe some information is haproxy vulnerable
> against this attacks?
>
> https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md
Yes I had a look after
Hi.
Have anyone seen this and maybe some information is haproxy vulnerable against
this attacks?
https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md
On HN is also some Info's available.
https://news.ycombinator.com/item?id=20688178
Best regards
On Tue, Aug 13, 2019 at 11:49:20AM +0200, Willy Tarreau wrote:
> Excellent, I think you caught it! I can reproduce it here, except that
> it doesn't last long, as soon as I get the socket error it's done. So
> we indeed broke something in the connection setup.
Bug kindly brought to you by your
Hi Cyril,
On Tue, Aug 13, 2019 at 11:38:23AM +0200, Cyril Bonté wrote:
> Hi Willy,
>
> This morning, I found another case where haproxy 2.0 abnormally consumes the
> cpu. It occured on my laptop when my network was not setup yet.
>
> I could find a simple reproducer :
> listen test
> mode
Hi Willy,
This morning, I found another case where haproxy 2.0 abnormally consumes
the cpu. It occured on my laptop when my network was not setup yet.
I could find a simple reproducer :
listen test
mode http
bind :
server s1 10.0.0.1:
then, curl http://localhost:/
7 matches
Mail list logo
