On Mon, Apr 15, 2024 at 10:18:19AM +0200, Aleksandar Lazic wrote:
> Hi.
>
> The "https://github.com/criteo/haproxy-spoe-go; is archived since Nov 7,
> 2023 and there is a fork from that repo https://github.com/go-spop/spoe
> Can we add this info to the wiki page?
>
> There is also a rust
Hi.
The "https://github.com/criteo/haproxy-spoe-go; is archived since Nov 7, 2023
and there is a fork from that repo https://github.com/go-spop/spoe
Can we add this info to the wiki page?
There is also a rust implementation
https://github.com/vkill/haproxy-spoa-example which could be added.
Dear list!
Author: songliumeng <161319869+songlium...@users.noreply.github.com>
Number of patches: 1
This is an automated relay of the Github pull request:
Update LICENSE to match license requirement of the upstream repository
Patch title(s):
Update LICENSE to match license requi
Hi Tim!
On Thu, Feb 08, 2024 at 07:55:23PM +0100, Tim Duesterhus wrote:
> No functional change, but this upgrade is required, due to the v3 runtime
> being
> deprecated:
>
> > Node.js 16 actions are deprecated. Please update the following actions to
> > use
> >
No functional change, but this upgrade is required, due to the v3 runtime being
deprecated:
> Node.js 16 actions are deprecated. Please update the following actions to use
> Node.js 20: actions/cache@v3. For more information see:
> https://github.blog/changelog/2023-09-22-githu
On Fri, Jan 26, 2024 at 06:35:09PM +, David Carlier wrote:
> >
> > It broke the CI on the "all features" build:
> >
> >
> > https://github.com/haproxy/haproxy/actions/runs/7671640626/job/20910459829
> >
> > /usr/bin/ld: cannot find -lcurl: No such file or directory
> > /usr/bin/ld: cannot find
>
> It broke the CI on the "all features" build:
>
>
> https://github.com/haproxy/haproxy/actions/runs/7671640626/job/20910459829
>
> /usr/bin/ld: cannot find -lcurl: No such file or directory
> /usr/bin/ld: cannot find -lzip: No such file or directory
>
> I'm surprised because CURL_LDFLAGS and
On Fri, Jan 26, 2024 at 06:57:57PM +0100, Willy Tarreau wrote:
> On Fri, Jan 26, 2024 at 05:38:20PM +, David Carlier wrote:
> > I m good with your version. Thanks !
>
> Great, now merged, thanks!
> Willy
It broke the CI on the "all features" build:
On Fri, Jan 26, 2024 at 05:38:20PM +, David Carlier wrote:
> I m good with your version. Thanks !
Great, now merged, thanks!
Willy
I m good with your version. Thanks !
On Fri, Jan 26, 2024 at 5:35 PM Willy Tarreau wrote:
> On Fri, Jan 26, 2024 at 04:41:36PM +, David Carlier wrote:
> > Hi,
> >
> > Please find the revised patch.
>
> OK thanks, it looks good and addresses the build issue.
>
> I noticed that when building
On Fri, Jan 26, 2024 at 04:41:36PM +, David Carlier wrote:
> Hi,
>
> Please find the revised patch.
OK thanks, it looks good and addresses the build issue.
I noticed that when building with the dummy lib, we continue to link
with -lstdc++ even if it's not used (unless DEVICEATLAS_NOCACHE=1)
Hi,
Please find the revised patch.
Regards.
On Fri, Jan 26, 2024 at 4:28 PM Willy Tarreau wrote:
> Hi David,
>
> On Thu, Jan 25, 2024 at 09:26:24AM +, David Carlier wrote:
> > Finally the last piece related to the da's dummy update and da.c changes.
>
> Thanks. I'm
Hi David,
On Thu, Jan 25, 2024 at 09:26:24AM +, David Carlier wrote:
> Finally the last piece related to the da's dummy update and da.c changes.
Thanks. I'm getting the following build error:
addons/deviceatlas/da.c: In function 'da_haproxy_checkinst':
addons/deviceatlas/da.c:284
Hi here the first patch of the series related to the da's addon build
change.
From 6ee26e72c1d38a9e83c6c64e40c3ca50aa3f9ff9 Mon Sep 17 00:00:00 2001
From: David Carlier
Date: Thu, 25 Jan 2024 09:00:14 +
Subject: [PATCH 1/3] BUILD/MEDIUM: deviceatlas: addon build rework.
- Removing the legacy
Here the second patch dedicated solely to the doc.
From 9381e5e844aebd161299467bdfbf501c86409b6a Mon Sep 17 00:00:00 2001
From: David Carlier
Date: Thu, 25 Jan 2024 09:09:07 +
Subject: [PATCH 2/3] DOC: deviceatlas: update to be in line with the v3 api.
Reflecting here all the changes
Finally the last piece related to the da's dummy update and da.c changes.
From df705a30e7d6ce41b61ac7a3e670158b2b2cac25 Mon Sep 17 00:00:00 2001
From: David Carlier
Date: Thu, 25 Jan 2024 09:11:18 +
Subject: [PATCH 3/3] BUILD/MEDIUM: deviceatlas: updating the addon part.
- Reflecing
...@haproxy.com
Subject: [EXTERNAL] Re: [PATCH 0/1] Update ssl_fc_curve/ssl_bc_curve sample
fetch
On 2024-01-08 21:01, Mariam John wrote:
>
> Thank you Willy for the update. Appreciate it. Please take your time.
> I totally understand. Just wanted to make sure it wasn’t lost or
> forgotten abou
On 2024-01-08 21:01, Mariam John wrote:
Thank you Willy for the update. Appreciate it. Please take your time.
I totally understand. Just wanted to make sure it wasn’t lost or
forgotten about.
Thank you once again.
Regards,
Mariam.
Hello Mariam,
Thank you for your contribution, I merged
On Mon, Jan 08, 2024 at 08:01:07PM +, Mariam John wrote:
> Thank you Willy for the update. Appreciate it. Please take your time. I
> totally understand. Just wanted to make sure it wasn't lost or forgotten
> about.
I knew you would naturally start to worry about it, I even
Thank you Willy for the update. Appreciate it. Please take your time. I totally
understand. Just wanted to make sure it wasn’t lost or forgotten about.
Thank you once again.
Regards,
Mariam.
From: Willy Tarreau
Date: Monday, January 8, 2024 at 1:25 PM
To: Mariam John
Cc: Mariam John
Hi Mariam,
On Mon, Jan 08, 2024 at 02:40:22PM +, Mariam John wrote:
> Happy new year!! Just wanted to see if this patch could move forward. I have
> made the changes recommended by William.
Yeah, we spoke about it this morning with William, he's still unpiling
his mailbox :-) Rest assured
...@haproxy.com
, Mariam John
Subject: [EXTERNAL] [PATCH 0/1] Update ssl_fc_curve/ssl_bc_curve sample fetch
Update ssl_fc_curve/ssl_fc_curve to use `SSL_get0_group_name` function
(available from the
OpenSSL v3.2 release onwards) to get the curve name. For OpenSSL versions >=3.0
and <3.2, we
will co
The function `smp_fetch_ssl_fc_ec` gets the curve name used during key
exchange. It currently uses the `SSL_get_negotiated_group`,
available since OpenSSLv3.0 to get the nid and derive the short name of the
curve from the nid. In OpenSSLv3.2, a new function,
`SSL_get0_group_name` was added that
Update ssl_fc_curve/ssl_fc_curve to use `SSL_get0_group_name` function
(available from the
OpenSSL v3.2 release onwards) to get the curve name. For OpenSSL versions >=3.0
and <3.2, we
will continue to use `SSL_get_negotiated_group` to get the curve name.
Mariam John (1):
BUG/MINO
On 2023-12-20 06:21, Mariam John wrote:
Update ssl_fc_curve/ssl_fc_curve to use `SSL_get0_group_name` function
(available from the
OpenSSL v3.2 release onwards) to get the curve name. For OpenSSL versions >=3.0
and <3.2, we
will continue to use `SSL_get_negotiated_group` to get the curv
Update ssl_fc_curve/ssl_fc_curve to use `SSL_get0_group_name` function
(available from the
OpenSSL v3.2 release onwards) to get the curve name. For OpenSSL versions >=3.0
and <3.2, we
will continue to use `SSL_get_negotiated_group` to get the curve name.
Mariam John (1):
BUG/MINO
The function `smp_fetch_ssl_fc_ec` gets the curve name used during key
exchange. It currently uses the `SSL_get_negotiated_group`,
available since OpenSSLv3.0 to get the nid and derive the short name of the
curve from the nid. In OpenSSLv3.2, a new function,
`SSL_get0_group_name` was added that
Hello,
I think I updated the manual correctly. Please let me know i'm missing
anything.
└─# git commit -a
[master f5af1ea98] Adding example for track
Committer: root
Your name and email address were configured
Dear list!
Author: Steven Lu
Number of patches: 1
This is an automated relay of the Github pull request:
BUG/MEDIUM: server-state: update server if the ports in config and
state match
Patch title(s):
BUG/MEDIUM: server-state: Only update server if the ports in config and
state still
Hello Kurtis,
On Thu, Oct 26, 2023 at 12:20:17PM +1000, Kurtis Miller wrote:
> https://www.haproxy.com/documentation/haproxy-configuration-manual/latest/#5.2-track
>
> Please add the following examples:
>
> backend A
> server a1 1.1.1.1:80 track B/b1
> server a2 1.1.1.2:80 track B/b1
>
>
https://www.haproxy.com/documentation/haproxy-configuration-manual/latest/#5.2-track
Please add the following examples:
backend A
server a1 1.1.1.1:80 track B/b1
server a2 1.1.1.2:80 track B/b1
backend B
server b1 2.2.2.2:80 check
this will help customers to better understand how the track
not surprised to learn that it was a PEBCAK
problem. :)
I have a certs webapp I wrote in PHP for Lets Encrypt certificate
generation and management. One of the things it does is update a
whitelist and reload haproxy, and it has an hourly cronjob to make sure
that the whitelist is always current.
I
From cc8fe58a8d2f8d47b03d03fd1048fe1b9babca70 Mon Sep 17 00:00:00 2001
From: Alexander Stephan
mailto:alexander.step...@sap.com>>
Date: Fri, 15 Sep 2023 12:18:10 +0200
Subject: [PATCH 3/4] LOW: connection: Add TLV update function
Until now, it was not possible to deliberatily change re
On Wed, Oct 04, 2023 at 08:52:39AM -0600, Shawn Heisey wrote:
> On 10/4/23 05:34, Remi Tricot-Le Breton wrote:
> > You just have to run the following commands :
> >
> > $ echo "update ssl ocsp-response " | socat
> > /path_to_socket/haproxy.sock -
>
&g
On 10/4/23 05:34, Remi Tricot-Le Breton wrote:
You just have to run the following commands :
$ echo "update ssl ocsp-response " | socat
/path_to_socket/haproxy.sock -
When I do this, the update is successful and shows in the logfile
created by rsyslogd ... but unlike when ha
On 04/10/2023 03:05, Shawn Heisey wrote:
On 10/3/23 01:33, Remi Tricot-Le Breton wrote:
This command relies on the same task that performs the automatic
update. What it does is basically add the certificate at the top of
the task's update list and wakes it up. The update is asynchronous so
we
On 10/3/23 01:33, Remi Tricot-Le Breton wrote:
This command relies on the same task that performs the automatic update.
What it does is basically add the certificate at the top of the task's
update list and wakes it up. The update is asynchronous so we can't
return a status to the CLI command
On 30/09/2023 09:20, Shawn Heisey wrote:
On 9/28/23 02:29, Remi Tricot-Le Breton wrote:
That's really strange, the OCSP update mechanism does not have
anything to do with proxies. Are you sure you did not have a crash
and autorestart of your haproxy ?
I did not think that I had autorestart
On 9/28/23 02:29, Remi Tricot-Le Breton wrote:
That's really strange, the OCSP update mechanism does not have anything
to do with proxies. Are you sure you did not have a crash and
autorestart of your haproxy ?
I did not think that I had autorestart for haproxy, but it turns out
. syslog:
That's really strange, the OCSP update mechanism does not have anything
to do with proxies. Are you sure you did not have a crash and
autorestart of your haproxy ?
Sep 27 15:00:01 - haproxy[3520801] Proxy web80 stopped (cumulated
conns: FE: 42, BE: 0).
Sep 27 15:00:01 - haproxy
/ssl/certs/local/REDACTED_org.wildcards.combined
.pem 1 "Update successful" 0 1
Sep 27 15:00:01 - haproxy[3545799] -:- [27/Sep/2023:15:00:01.795]
/etc/ssl/certs/local/REDACTED2.com.wildcards.combined.p
em 1 "Update successful" 0 1
Sep 27 15:00:01 - haproxy[3520801] -:- [27/S
From cc8fe58a8d2f8d47b03d03fd1048fe1b9babca70 Mon Sep 17 00:00:00 2001
From: Alexander Stephan
Date: Fri, 15 Sep 2023 12:18:10 +0200
Subject: [PATCH 3/4] LOW: connection: Add TLV update function
Until now, it was not possible to deliberatily change received TLVs
that are stored within
Hi Tim!
On Wed, Sep 06, 2023 at 04:57:29PM +0200, Tim Duesterhus wrote:
> No functional change, but we should keep this current.
Now merged, thank you!
Willy
' }}
steps:
-- uses: actions/checkout@v3
+- uses: actions/checkout@v4
- name: Install apt dependencies
run: |
sudo apt-get update
diff --git a/.github/workflows/cross-zoo.yml b/.github/workflows/cross-zoo.yml
index f2c8d7ad8..d9864e298 100644
--- a/.github/workflows/cross
On 8/15/23 19:17, Tristan wrote:
> A common error that can happen with let's encrypt certificates is if
the DNS
resolution provides an IPv6 address and your system does not have a valid
outgoing IPv6 route. In such a case, you can either create the appropriate
route or set the
Hi Shawn,
See the note at the end of
http://docs.haproxy.org/2.8/configuration.html#5.1-ocsp-update
Specifically:
> A common error that can happen with let's encrypt certificates is if the DNS
resolution provides an IPv6 address and your system does not have a valid
outgoing IPv6 ro
I've got another haproxy install on which I am trying to enable
automatic OCSP updating. The ones I asked about before are personal,
this one is for work.
When haproxy looks up the host where it can get OCSP responses, it is
getting an ipv6 address.
Aug 15 18:27:30 - haproxy[11234] -:-
On 07/07/2023 18:24, Willy Tarreau wrote:
On Fri, Jul 07, 2023 at 03:42:58PM +, Tristan wrote:
Also personally I have never understood the point of default server certs...
besides getting unwanted attention from censys/shodan/etc...
I remember some users who were hosting many
On Fri, Jul 07, 2023 at 03:42:58PM +, Tristan wrote:
> Also personally I have never understood the point of default server certs...
> besides getting unwanted attention from censys/shodan/etc...
I remember some users who were hosting many applications from internal
subsidiaries wanted to make
On 07/07/2023 16:34, Willy Tarreau wrote:
On Fri, Jul 07, 2023 at 03:06:52PM +, Tristan wrote:
The ocsp-update option should be between brackets
/etc/haproxy/ssl/mangadex.dev.pem [ocsp-update on] mangadex.dev
*.mangadex.dev
Oh that makes more sense indeed; should have guessed so since
On Fri, Jul 07, 2023 at 03:06:52PM +, Tristan wrote:
> > The ocsp-update option should be between brackets
> > /etc/haproxy/ssl/mangadex.dev.pem [ocsp-update on] mangadex.dev
> > *.mangadex.dev
>
> Oh that makes more sense indeed; should have guessed so since other crt
The ocsp-update option should be between brackets
/etc/haproxy/ssl/mangadex.dev.pem [ocsp-update on] mangadex.dev
*.mangadex.dev
Oh that makes more sense indeed; should have guessed so since other
crt-list bind params used those indeed...
- does the OCSP update mechanism update the files
Hello Tristan,
On 06/07/2023 13:24, Tristan wrote:
Hello,
I'm trying to make use of the new ocsp-update mechanism, and finding
no success (yet).
I've migrated my crt bind arguments to a crt-list argument (+ relevant
file) and that loads in and gets used fine, but despite having
"
Hello,
I'm trying to make use of the new ocsp-update mechanism, and finding no
success (yet).
I've migrated my crt bind arguments to a crt-list argument (+ relevant
file) and that loads in and gets used fine, but despite having
"ocsp-update on" on the lines, I'm not seeing any o
I am reaching out because...
Would you be interested in SATELLITE 2023 Updated Attendees Database?.
Who attends: -
Manufacturer/Ground systems/Integrater, Business & information, Satelite
Operator/Carrier, Militery/Government, Commercial market, Media & communications
Other...
Record in the
branch, which is the one that will give you the least surprise or
changes. Please do not ask for help upgrading from outdated versions,
if you didn't care about updating in 5 years, it's unlikely that anyone
will care about helping you to catch up.
For those who for some reasons cannot update right
Le 9/26/22 à 17:27, Fatih Acar a écrit :
This patch adds support to the following authentication methods:
- AUTH_REQ_GSS (7)
- AUTH_REQ_SSPI (9)
- AUTH_REQ_SASL (10)
Note that since AUTH_REQ_SASL allows multiple authentication mechanisms
such as SCRAM-SHA-256 or SCRAM-SHA-256-PLUS, the auth
Le 9/26/22 à 17:27, Fatih Acar a écrit :
This patch adds support to the following authentication methods:
- AUTH_REQ_GSS (7)
- AUTH_REQ_SSPI (9)
- AUTH_REQ_SASL (10)
Note that since AUTH_REQ_SASL allows multiple authentication mechanisms
such as SCRAM-SHA-256 or SCRAM-SHA-256-PLUS, the auth
This patch adds support to the following authentication methods:
- AUTH_REQ_GSS (7)
- AUTH_REQ_SSPI (9)
- AUTH_REQ_SASL (10)
Note that since AUTH_REQ_SASL allows multiple authentication mechanisms
such as SCRAM-SHA-256 or SCRAM-SHA-256-PLUS, the auth payload length may
vary since the method is
cript simply runs:
>
> echo "show servers state" | socat /var/run/haproxy/admin.sock - > \
> /var/lib/haproxy/server_state
>
> I've noticed that when I change the port on a backend server and reload,
> haproxy does not update the port for that server. I have to shu
d that when I change the port on a backend server and reload,
haproxy does not update the port for that server. I have to shut down haproxy,
delete the state file, then start it back up for it to update the port
(changing the port and renaming the server, reloading, then renaming it back
and re
Dear David,
I hope you are doing well?
I'm aware it's been a while since my last email regarding our recruiting
situation. Apologies for the radio silence from my side.
I wanted to get back in touch and let you know that after reviewing our hiring
plans and aligning it to our goals, we
On Thu, Apr 28, 2022 at 11:59:39AM +0500, ??? wrote:
> Hello,
>
> small patch to sync with current LibreSSL release
Merged, thank you Ilya!
Willy
Hello,
small patch to sync with current LibreSSL release
Ilya
From 425d2810e8b2b9288c3abbb05fefacf5e9044b9d Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu, 28 Apr 2022 11:46:53 +0500
Subject: [PATCH] CI: github actions: update LibreSSL to 3.5.2
LibreSSL-3.5.2 was released on Apr 23nd
On Mon, Apr 11, 2022 at 11:02:04PM +0500, ??? wrote:
> From: Ilya Shipitsin
> Date: Mon, 11 Apr 2022 22:25:35 +0500
> Subject: [PATCH] CI: cirrus: switch to FreeBSD-13.0
>
> we use outdated FreeBSD-12.2, which is outdated, let us update
> to the actual release
Hello,
small cirrus-ci patch
Ilya
From 17e3719e05a04b3064b2783ef89cc7bc7c3524e9 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Mon, 11 Apr 2022 22:25:35 +0500
Subject: [PATCH] CI: cirrus: switch to FreeBSD-13.0
we use outdated FreeBSD-12.2, which is outdated, let us update
to the actual
On Sat, Apr 09, 2022 at 10:08:41PM +0200, Tim Duesterhus wrote:
> No functional change, but we should keep this current.
(...)
both patches applied, thank you Tim!
Willy
T=1"
steps:
-- uses: actions/checkout@v2
+- uses: actions/checkout@v3
- name: Install apt dependencies
run: |
sudo apt-get update
diff --git a/.github/workflows/musl.yml b/.github/workflows/musl.yml
index aba3f4e14..5a6b46a7b 100644
--- a/.github/workflows/mu
No functional changes for our use case, but we should keep this current.
---
.github/workflows/vtest.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/vtest.yml b/.github/workflows/vtest.yml
index e413b20f5..7a1c1ef62 100644
---
On Sun, Mar 27, 2022 at 12:02:23PM +0500, ??? wrote:
> Hello,
>
> minor openssl update in CI.
Applied, thank you Ilya!
Willy
Hello,
minor openssl update in CI.
Ilya
From ef50b14a80b0a54e4d71688e19bb91369fdbf5a7 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Sun, 27 Mar 2022 10:51:51 +0500
Subject: [PATCH] CI: github actions: update OpenSSL to 3.0.2
---
.github/matrix.py | 2 +-
1 file changed, 1 insertion
On Thu, Jan 27, 2022 at 06:34:23PM +, David Carlier wrote:
> Hi willy and thanks for the review. Indeed I forgot about the dummy part,
> changes present in the last patch.
Thank you. I had to swap the last two patches so that it always
builds, but that's OK this way, so I've now merged it.
t; > Date: Fri, 21 Jan 2022 20:57:27 +
> > Subject: [PATCH 3/3] MEDIUM: deviceatlas doc and build update.
>
> "MEDIUM: da: doc and build for new runtime update service" ?
>
> > diff --git a/Makefile b/Makefile
> > index af0f5cc87..e6f2e04ad 100644
&g
On Thu, Jan 27, 2022 at 5:29 PM Willy Tarreau wrote:
> On Fri, Jan 21, 2022 at 09:04:25PM +, David Carlier wrote:
> > Second patch of the patchset concerning the update of the addon itself.
>
> > From d541d8dfd8aa0290625b3824bd6b44d2861e997f Mon Sep 17 00:00:00 2001
>
data file
> download scheduler service.
> ^^^
> Please always place a colon after the subsystem. Also, previously it
> was referred to as "da", it would be better to stay consistent in order
> to more easily list all such related changes.
>
> > New
On Fri, Jan 21, 2022 at 09:05:18PM +, David Carlier wrote:
> From e3f520ebd4f23fe42a1068ee2d9b42fd529241e8 Mon Sep 17 00:00:00 2001
> From: David Carlier
> Date: Fri, 21 Jan 2022 20:57:27 +
> Subject: [PATCH 3/3] MEDIUM: deviceatlas doc and build update.
"MEDIUM:
On Fri, Jan 21, 2022 at 09:04:25PM +, David Carlier wrote:
> Second patch of the patchset concerning the update of the addon itself.
> From d541d8dfd8aa0290625b3824bd6b44d2861e997f Mon Sep 17 00:00:00 2001
> From: David Carlier
> Date: Fri, 21 Jan 2022 20:51:20 +
> Subj
r
to more easily list all such related changes.
> New specialized service to daily handle the update of download file without
> interruption of service and to be preemptively started before HAProxy.
While I do know from your private explanation that it's an external
service, it's not immediat
Last patch of the patchset concerning the doc and the build.
Thanks in advance.
From e3f520ebd4f23fe42a1068ee2d9b42fd529241e8 Mon Sep 17 00:00:00 2001
From: David Carlier
Date: Fri, 21 Jan 2022 20:57:27 +
Subject: [PATCH 3/3] MEDIUM: deviceatlas doc and build update.
Mentions of the new
Second patch of the patchset concerning the update of the addon itself.
From d541d8dfd8aa0290625b3824bd6b44d2861e997f Mon Sep 17 00:00:00 2001
From: David Carlier
Date: Fri, 21 Jan 2022 20:51:20 +
Subject: [PATCH 2/3] MEDIUM: deviceatlas update of the main module.
The DeviceAtlas addon can
: deviceatlas new optional data file download
scheduler service.
New specialized service to daily handle the update of download file without
interruption of service and to be preemptively started before HAProxy.
Signed-off-by: David Carlier
---
addons/deviceatlas/Makefile | 49 +
addons
On Sat, Dec 25, 2021 at 02:15:38PM +0500, ??? wrote:
> Hello,
>
> the attached patch updates OpenSSL to recently released 3.0.1
And applied as well, thanks. I thought I already took it but I was
apparently mistaken.
Willy
gentle ping
сб, 25 дек. 2021 г. в 14:15, Илья Шипицин :
> Hello,
>
> the attached patch updates OpenSSL to recently released 3.0.1
>
> Ilya
>
Hello,
the attached patch updates OpenSSL to recently released 3.0.1
Ilya
From 4ff432aa2dad464bda19b1dab48cc998aff59feb Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Sat, 25 Dec 2021 14:01:52 +0500
Subject: [PATCH] CI: github actions: update OpenSSL to 3.0.1
OpenSSL-3.0.1 was released
On Fri, Nov 26, 2021 at 08:51:56PM +, David CARLIER wrote:
> Hi
>
> Here the following up for the apple system allocator (aka libmalloc).
Thank you David, now merged (second version).
Willy
Sorry the same patch removing useless line :)
On Fri, 26 Nov 2021 at 20:51, David CARLIER wrote:
>
> Hi
>
> Here the following up for the apple system allocator (aka libmalloc).
>
> Cheers.
>
> Kind regards.
0001-MEDIUM-pool-Following-up-on-previous-pool-trimming-u.patch
Description: Binary
Hi
Here the following up for the apple system allocator (aka libmalloc).
Cheers.
Kind regards.
0001-MEDIUM-pool-Following-up-on-previous-pool-trimming-u.patch
Description: Binary data
Hi support,
I have installed haproxy-1.8.30 from sources on redhat 7.9. I would like to
know what procedure I can follow to update that when will be releases next
minor version
Thanks a lot
Emiliano
[AVIO SpA]<http://www.avio.com/>
Emiliano Mastroianni
IT Network & Security
T + 39
On Fri, Mar 19, 2021 at 06:58:44PM +0100, Tim Düsterhus wrote:
> Willy,
>
> Am 19.03.21 um 18:52 schrieb ???:
> > let us update libressl to 3.2.5 and revert previously disabled tls session
> > resumption in reg-test
> >
>
> Both of these look good to me
Willy,
Am 19.03.21 um 18:52 schrieb Илья Шипицин:
> let us update libressl to 3.2.5 and revert previously disabled tls session
> resumption in reg-test
>
Both of these look good to me.
Best regards
Tim Düsterhus
Hello,
let us update libressl to 3.2.5 and revert previously disabled tls session
resumption in reg-test
Ilya
From 6453e067c877db1ac98f92220dccebab572eaaf1 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Fri, 19 Mar 2021 22:29:16 +0500
Subject: [PATCH 1/2] CI: github actions: update
Le 11/02/2021 à 19:35, Илья Шипицин a écrit :
Hello,
attached patch fix freebsd builds.
Ilya
Thanks, now merged !
--
Christopher Faulet
Willy,
Am 11.02.21 um 19:35 schrieb Илья Шипицин:
> attached patch fix freebsd builds.
This one looks good to me. Please take it.
Best regards
Tim Düsterhus
Hello,
attached patch fix freebsd builds.
Ilya
From 6b2c848cfa563f5b0c8cd34f3fa5ce99847d91a3 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu, 11 Feb 2021 23:32:30 +0500
Subject: [PATCH] CI: cirrus: update FreeBSD image to 12.2
we already tried to run FreeBSD-stable. it is pain,
so we
I guess you'll need to have a preliminary
> patch that only changes the function's API. In addition, please update
> the comment on top of the function to reflect your API change, because
> this is definitely wrong:
>
>/* Tries to report the executable path name on plat
re the patch mentioning FreeBSD+Mac only does
that and nothing else. As such I guess you'll need to have a preliminary
patch that only changes the function's API. In addition, please update
the comment on top of the function to reflect your API change, because
this is definitely wrong:
/* Tri
Hi
Here a little patch proposal. Since it is relatively self-contained
change, it could be possibly backported smoothly.
Kind regards.
0001-BUILD-MINOR-ha_alert-report-full-path-for-FreeBSD-an.patch
Description: Binary data
Hi David,
On Thu, Dec 10, 2020 at 09:58:34AM +, David Carlier wrote:
> Hi, here a tiny change in the MAINTAINERS file.
>
> Please backporting as much as possible.
Now merged, thank you!
Willy
Hi, here a tiny change in the MAINTAINERS file.
Please backporting as much as possible.
Thanks in advance.
Kind regards.
0001-DOC-email-change-of-the-DeviceAtlas-maintainer.patch
Description: Binary data
On Wed, Dec 02, 2020 at 09:19:19PM +, David CARLIER wrote:
> On Wed, 2 Dec 2020 at 19:27, Willy Tarreau wrote:
> >
> > Hi David,
> >
> > On Wed, Dec 02, 2020 at 10:50:52AM +, David CARLIER wrote:
> > > Hi, heere a little build update for DragonFlyBSD pr
1 - 100 of 289 matches
Mail list logo
