On Tue, Sep 15, 2020 at 06:43:11PM +0100, Jonathan Matthews wrote:
> On Tue, 15 Sep 2020 at 16:42, Tim Düsterhus wrote:
>
> > Why not use the Tab (0x09) as separator and make the output a proper TSV?
>
>
> I’m only 2% joking when I point out that ASCII already has single-byte
> inter-field and
On Tue, Sep 15, 2020 at 05:39:18PM +0200, Tim Düsterhus wrote:
> William,
>
> Am 15.09.20 um 17:36 schrieb William Lallemand:
> > Oh right... the space in "[was: ]" is troublesome for cutting the string,
> > we must remove it.
> >
>
> Why not use the Tab (0x09) as separator and make the output a
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses t
Hi,
I tested for openssl-1.1.1g.tar.gz from openssl.org in Linux Mint 19.3:
$ patch -p1 < reorder-sigalgs.patch
patching file ssl/t1_lib.c
./config
make
make test
Test Summary Report
---
../test/recipes/80-test_ssl_new.t (Wstat: 256 Tests: 29
Failed: 1)
Fai
On Tue, 15 Sep 2020 at 16:42, Tim Düsterhus wrote:
> Why not use the Tab (0x09) as separator and make the output a proper TSV?
I’m only 2% joking when I point out that ASCII already has single-byte
inter-field and inter-record delimiters defined, just waiting to be used
... :-)
https://ronaldd
> Em 15 de set de 2020, à(s) 12:36, William Lallemand
> escreveu:
>
> Oh right... the space in "[was: ]" is troublesome for cutting the string,
> we must remove it.
It's not a problem at all when using chunks of fixed size, even if columns
differ between them, and the lay out ([was: ...]) r
William,
Am 15.09.20 um 17:36 schrieb William Lallemand:
> Oh right... the space in "[was: ]" is troublesome for cutting the string,
> we must remove it.
>
Why not use the Tab (0x09) as separator and make the output a proper TSV?
Best regards
Tim Düsterhus
On Tue, Sep 15, 2020 at 11:52:15AM -0300, Joao Morais wrote:
>
>
> > Em 14 de set de 2020, à(s) 19:14, William Lallemand
> > escreveu:
> >
> > Hello,
> >
> > On Mon, Sep 14, 2020 at 12:09:21PM -0300, Joao Morais wrote:
> >> Hello list, I'm working on an automation around haproxy process
> >>
> Em 14 de set de 2020, à(s) 19:14, William Lallemand
> escreveu:
>
> Hello,
>
> On Mon, Sep 14, 2020 at 12:09:21PM -0300, Joao Morais wrote:
>> Hello list, I'm working on an automation around haproxy process
>> lifecycle in master-worker mode. It's working nice but I'm not
>> confident that
Hi,
Last time I saw this error it involved TLS decryption by firewalls that didn't
support RSA-PSS. Why they blow up
when the new, more secure RSA-PSS signature algorithms are used beats me, but
it's principally _on them_ for not supporting the latest IETF standards.
Attached is a patch that re
Hi!
We can not get haproxy-ingress to work with TLS authentication. Only
option to get this work is by using force-tlsv12 and then only Chrome
works. Problem is TLS handshake decrypt error when using RSA-PSS
signature algorithm, handshake fails every time. When we use
force-tlsv12, only Chrom
Brad, can you also review cirrus-ci job for freebsd?
On Tue, Sep 15, 2020, 1:06 PM Brad Smith wrote:
> On 9/15/2020 3:45 AM, Lukas Tribus wrote:
> > On Tue, 15 Sep 2020 at 09:05, Brad Smith wrote:
> NetBSD 8.0 adds support for accept4() and closefrom(). Enable
> getaddrinfo().
> >>> We jus
On 9/15/2020 3:45 AM, Lukas Tribus wrote:
On Tue, 15 Sep 2020 at 09:05, Brad Smith wrote:
NetBSD 8.0 adds support for accept4() and closefrom(). Enable getaddrinfo().
We just had to disable threading on OpenBSD 6.7 for the build to succeed:
https://github.com/haproxy/haproxy/issues/725
Did y
On Tue, 15 Sep 2020 at 09:05, Brad Smith wrote:
> >> NetBSD 8.0 adds support for accept4() and closefrom(). Enable
> >> getaddrinfo().
> > We just had to disable threading on OpenBSD 6.7 for the build to succeed:
> >
> > https://github.com/haproxy/haproxy/issues/725
> >
> > Did you actually test
On Tue, Sep 15, 2020 at 09:24:32AM +0200, Willy Tarreau wrote:
(...)
> There's no such ongoing work that I'm aware of but that has always
> been a subject of interest to me (I even wrote down the algorithm to
> compute weights by measured response times using a low-pass filter a
> decade ago but I
Hi Pavlos!
On Sat, Sep 12, 2020 at 11:45:12AM +0200, Pavlos Parissis wrote:
> Hi old friends!,
>
> Is in the roadmap the addition of a circuit breaking which adapts its
> settings using real-time data?
> I believe we discussed this in the last HAProxyConf with a group of people,
> but I don't r
This updates the feature flags for FreeBSD.
FreeBSD 10 adds support for accept4().
Enable getaddrinfo().
>From the FreeBSD port / package.
diff --git a/Makefile b/Makefile
index 934ca1666..e69870595 100644
--- a/Makefile
+++ b/Makefile
@@ -363,11 +363,11 @@ ifeq ($(TARGET),solaris)
TARGET_
On 9/14/2020 5:39 AM, Lukas Tribus wrote:
Hello Brad,
On Sun, 13 Sep 2020 at 09:08, Brad Smith wrote:
The following diff updates the feature flags for Solaris / FreeBSD / NetBSD /
OpenBSD.
Bump the baseline Solaris to 9 which intruduced closefrom().
FreeBSD 10 is already EOL for support but
On Tue, Sep 15, 2020 at 11:46:02AM +0500, ??? wrote:
> ping
Sorry, I missed it, now merged.
Thanks!
Willy
19 matches
Mail list logo