<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/haproxy.git/include/haproxy/openssl-compat.h, branch master</title>
<subtitle>github.com: haproxy/haproxy.git
</subtitle>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/'/>
<entry>
<title>BUILD: ssl: get0_verified chain is available on libreSSL</title>
<updated>2023-05-15T13:16:15+00:00</updated>
<author>
<name>William Lallemand</name>
<email>wlallemand@haproxy.org</email>
</author>
<published>2023-05-15T12:42:28+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=d0c363486cb2a9b0d4374fc236ff55f842a2a5e7'/>
<id>d0c363486cb2a9b0d4374fc236ff55f842a2a5e7</id>
<content type='text'>
Define HAVE_SSL_get0_verified_chain when it's using libreSSL &gt;= 3.3.6.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Define HAVE_SSL_get0_verified_chain when it's using libreSSL &gt;= 3.3.6.
</pre>
</div>
</content>
</entry>
<entry>
<title>BUILD: ssl: ssl_c_r_dn fetches uses  functiosn only available since 1.1.1</title>
<updated>2023-05-15T10:07:52+00:00</updated>
<author>
<name>William Lallemand</name>
<email>wlallemand@haproxy.org</email>
</author>
<published>2023-05-15T10:05:55+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=6e0c39d7ac3282bc255f742da36402434af0db77'/>
<id>6e0c39d7ac3282bc255f742da36402434af0db77</id>
<content type='text'>
Fix the openssl build with older openssl version by disabling the new
ssl_c_r_dn fetch.

This also disable the ssl_client_samples.vtc file for OpenSSL version
older than 1.1.1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix the openssl build with older openssl version by disabling the new
ssl_c_r_dn fetch.

This also disable the ssl_client_samples.vtc file for OpenSSL version
older than 1.1.1
</pre>
</div>
</content>
</entry>
<entry>
<title>MINOR: ssl: allow to change the server signature algorithm</title>
<updated>2023-05-04T20:43:18+00:00</updated>
<author>
<name>William Lallemand</name>
<email>wlallemand@haproxy.org</email>
</author>
<published>2023-05-04T13:33:55+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=1d3c822300003bf40f4d723109c690ad2944baf2'/>
<id>1d3c822300003bf40f4d723109c690ad2944baf2</id>
<content type='text'>
This patch introduces the "sigalgs" keyword for the bind line, which
allows to configure the list of server signature algorithms negociated
during the handshake. Also available as "ssl-default-bind-sigalgs" in
the default section.

This patch was originally written by Bruno Henc.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch introduces the "sigalgs" keyword for the bind line, which
allows to configure the list of server signature algorithms negociated
during the handshake. Also available as "ssl-default-bind-sigalgs" in
the default section.

This patch was originally written by Bruno Henc.
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG/MINOR: ssl: Undefined reference when building with OPENSSL_NO_DEPRECATED</title>
<updated>2023-04-03T09:46:54+00:00</updated>
<author>
<name>Remi Tricot-Le Breton</name>
<email>rlebreton@haproxy.com</email>
</author>
<published>2023-04-03T09:17:26+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=26e1432436723175962bcf4b48475dad65308a5c'/>
<id>26e1432436723175962bcf4b48475dad65308a5c</id>
<content type='text'>
If OPENSSL_NO_DEPRECATED is set, we get a 'error: ‘RSA_PKCS1_PADDING’
undeclared' when building jwt.c. The symbol is not deprecated, we are
just missing an include.

This was raised in GitHub issue #2098.
It does not need to be backported.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If OPENSSL_NO_DEPRECATED is set, we get a 'error: ‘RSA_PKCS1_PADDING’
undeclared' when building jwt.c. The symbol is not deprecated, we are
just missing an include.

This was raised in GitHub issue #2098.
It does not need to be backported.
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG/MINOR: ssl: Fix compilation with OpenSSL 1.0.2 (missing ECDSA_SIG_set0)</title>
<updated>2023-01-19T10:13:51+00:00</updated>
<author>
<name>Remi Tricot-Le Breton</name>
<email>rlebreton@haproxy.com</email>
</author>
<published>2023-01-18T16:29:54+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=bb35e1f5aa69f55f588e060fee6098db37abe94c'/>
<id>bb35e1f5aa69f55f588e060fee6098db37abe94c</id>
<content type='text'>
This function was introduced in OpenSSL 1.1.0. Prior to that, the
ECDSA_SIG structure was public.
This function was used in commit 5a8f02ae "BUG/MEDIUM: jwt: Properly
process ecdsa signatures (concatenated R and S params)".

This patch needs to be backported up to branch 2.5 alongside commit
5a8f02ae.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This function was introduced in OpenSSL 1.1.0. Prior to that, the
ECDSA_SIG structure was public.
This function was used in commit 5a8f02ae "BUG/MEDIUM: jwt: Properly
process ecdsa signatures (concatenated R and S params)".

This patch needs to be backported up to branch 2.5 alongside commit
5a8f02ae.
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "BUILD: ssl: add ECDSA_SIG_set0() for openssl &lt; 1.1 or libressl &lt; 2.7"</title>
<updated>2023-01-19T10:13:24+00:00</updated>
<author>
<name>William Lallemand</name>
<email>wlallemand@haproxy.org</email>
</author>
<published>2023-01-19T10:08:42+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=2edc6d0301825327b6b5acb6acd1c68701bb104e'/>
<id>2edc6d0301825327b6b5acb6acd1c68701bb104e</id>
<content type='text'>
This reverts commit d65791e26c12b57723f2feb7eacdbbd99601371b.

Conflict with the patch which was originally written and lacks the
BN_clear_free() and the NULL check.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit d65791e26c12b57723f2feb7eacdbbd99601371b.

Conflict with the patch which was originally written and lacks the
BN_clear_free() and the NULL check.
</pre>
</div>
</content>
</entry>
<entry>
<title>BUILD: ssl: add ECDSA_SIG_set0() for openssl &lt; 1.1 or libressl &lt; 2.7</title>
<updated>2023-01-19T09:57:00+00:00</updated>
<author>
<name>Willy Tarreau</name>
<email>w@1wt.eu</email>
</author>
<published>2023-01-19T09:50:13+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=d65791e26c12b57723f2feb7eacdbbd99601371b'/>
<id>d65791e26c12b57723f2feb7eacdbbd99601371b</id>
<content type='text'>
Commit 5a8f02ae6 ("BUG/MEDIUM: jwt: Properly process ecdsa signatures
(concatenated R and S params)") makes use of ECDSA_SIG_set0() which only
appeared in openssl-1.1.0 and libressl 2.7, and breaks the build before.
Let's just do what it minimally does (only assigns the two fields to the
destination).

This will need to be backported where the commit above is, likely 2.5.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Commit 5a8f02ae6 ("BUG/MEDIUM: jwt: Properly process ecdsa signatures
(concatenated R and S params)") makes use of ECDSA_SIG_set0() which only
appeared in openssl-1.1.0 and libressl 2.7, and breaks the build before.
Let's just do what it minimally does (only assigns the two fields to the
destination).

This will need to be backported where the commit above is, likely 2.5.
</pre>
</div>
</content>
</entry>
<entry>
<title>MEDIUM: ssl: add minimal WolfSSL support with OpenSSL compatibility mode</title>
<updated>2022-11-24T10:29:03+00:00</updated>
<author>
<name>Uriah Pollock</name>
<email>uriah@wolfssl.com</email>
</author>
<published>2022-11-23T15:41:25+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=3cbf09ed6411d6e28020eefd91f0e70d5b64bcb5'/>
<id>3cbf09ed6411d6e28020eefd91f0e70d5b64bcb5</id>
<content type='text'>
This adds a USE_OPENSSL_WOLFSSL option, wolfSSL must be used with the
OpenSSL compatibility layer. This must be used with USE_OPENSSL=1.

WolfSSL build options:

   ./configure --prefix=/opt/wolfssl --enable-haproxy

HAProxy build options:

  USE_OPENSSL=1 USE_OPENSSL_WOLFSSL=1 WOLFSSL_INC=/opt/wolfssl/include/ WOLFSSL_LIB=/opt/wolfssl/lib/ ADDLIB='-Wl,-rpath=/opt/wolfssl/lib'

Using at least the commit 54466b6 ("Merge pull request #5810 from
Uriah-wolfSSL/haproxy-integration") from WolfSSL. (2022-11-23).

This is still to be improved, reg-tests are not supported yet, and more
tests are to be done.

Signed-off-by: William Lallemand &lt;wlallemand@haproxy.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This adds a USE_OPENSSL_WOLFSSL option, wolfSSL must be used with the
OpenSSL compatibility layer. This must be used with USE_OPENSSL=1.

WolfSSL build options:

   ./configure --prefix=/opt/wolfssl --enable-haproxy

HAProxy build options:

  USE_OPENSSL=1 USE_OPENSSL_WOLFSSL=1 WOLFSSL_INC=/opt/wolfssl/include/ WOLFSSL_LIB=/opt/wolfssl/lib/ ADDLIB='-Wl,-rpath=/opt/wolfssl/lib'

Using at least the commit 54466b6 ("Merge pull request #5810 from
Uriah-wolfSSL/haproxy-integration") from WolfSSL. (2022-11-23).

This is still to be improved, reg-tests are not supported yet, and more
tests are to be done.

Signed-off-by: William Lallemand &lt;wlallemand@haproxy.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>MINOR: ssl: Add 'show ssl providers' cli command and providers list in -vv option</title>
<updated>2022-04-21T12:54:45+00:00</updated>
<author>
<name>Remi Tricot-Le Breton</name>
<email>rlebreton@haproxy.com</email>
</author>
<published>2022-04-21T10:06:41+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=f87c67e5e46fd9c57e6f7c0e94372ccdd4a45c11'/>
<id>f87c67e5e46fd9c57e6f7c0e94372ccdd4a45c11</id>
<content type='text'>
Starting from OpenSSLv3, providers are at the core of cryptography
functions. Depending on the provider used, the way the SSL
functionalities work could change. This new 'show ssl providers' CLI
command allows to show what providers were loaded by the SSL library.
This is required because the provider configuration is exclusively done
in the OpenSSL configuration file (/usr/local/ssl/openssl.cnf for
instance).
A new line is also added to the 'haproxy -vv' output containing the same
information.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Starting from OpenSSLv3, providers are at the core of cryptography
functions. Depending on the provider used, the way the SSL
functionalities work could change. This new 'show ssl providers' CLI
command allows to show what providers were loaded by the SSL library.
This is required because the provider configuration is exclusively done
in the OpenSSL configuration file (/usr/local/ssl/openssl.cnf for
instance).
A new line is also added to the 'haproxy -vv' output containing the same
information.
</pre>
</div>
</content>
</entry>
<entry>
<title>BUILD: ssl: add USE_ENGINE and disable the openssl engine by default</title>
<updated>2022-04-11T16:41:24+00:00</updated>
<author>
<name>William Lallemand</name>
<email>wlallemand@haproxy.org</email>
</author>
<published>2022-04-11T16:41:24+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/haproxy.git/commit/?id=d7bfbe233302d4307d1c950dd5146dd921dd01ad'/>
<id>d7bfbe233302d4307d1c950dd5146dd921dd01ad</id>
<content type='text'>
The OpenSSL engine API is deprecated starting with OpenSSL 3.0.

In order to have a clean build this feature is now disabled by default.
It can be reactivated with USE_ENGINE=1 on the build line.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The OpenSSL engine API is deprecated starting with OpenSSL 3.0.

In order to have a clean build this feature is now disabled by default.
It can be reactivated with USE_ENGINE=1 on the build line.
</pre>
</div>
</content>
</entry>
</feed>
