lp:~vcs-imports/ipfire/ipfire-2.x

Created by Jelmer Vernooij and last modified
Get this branch:
bzr branch lp:~vcs-imports/ipfire/ipfire-2.x

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
VCS imports
Project:
IPFire.org
Status:
Development

Import details

Import Status: Reviewed

This branch is an import of the HEAD branch of the Git repository at git://git.ipfire.org/ipfire-2.x.git.

The next import is scheduled to run .

Last successful import was .

Import started on izar and finished taking 10 seconds — see the log
Import started on alnitak and finished taking 15 seconds — see the log
Import started on alnitak and finished taking 15 seconds — see the log
Import started on alnitak and finished taking 15 seconds — see the log
Import started on izar and finished taking 10 seconds — see the log
Import started on alnitak and finished taking 15 seconds — see the log
Import started on izar and finished taking 10 seconds — see the log
Import started on izar and finished taking 10 seconds — see the log
Import started on alnitak and finished taking 15 seconds — see the log
Import started on alnitak and finished taking 15 seconds — see the log

Recent revisions

8774. By Michael Tremer <email address hidden> on 2021-04-17

core156: Avoid name collision in rootfiles

Signed-off-by: Michael Tremer <email address hidden>

8773. By Michael Tremer <email address hidden> on 2021-04-16

hostapd: Bump package version

Signed-off-by: Michael Tremer <email address hidden>

8772. By Michael Tremer <email address hidden> on 2021-04-16

hostaopd: Drop box with links to other configuration pages

We do not have this for any other feature and it clutters the UI.

Signed-off-by: Michael Tremer <email address hidden>

8771. By Michael Tremer <email address hidden> on 2021-04-16

hostapd: Find device by MAC address

With wireless device as members in bridges, we cannot predict the name
very well. So we will use the MAC address and find the correct device
name when we launch hostapd.

Signed-off-by: Michael Tremer <email address hidden>

8770. By Michael Tremer <email address hidden> on 2021-04-16

hostapd: Drop custom configuration from initscript

The initscript it setting a lot of options which are set by hostapd
which will fail to start the AP instead of using fire-and-forget.

Signed-off-by: Michael Tremer <email address hidden>

8769. By Michael Tremer <email address hidden> on 2021-04-12

rpcbind: Update initscript for moved binary

Signed-off-by: Michael Tremer <email address hidden>

8768. By Michael Tremer <email address hidden> on 2021-04-12

samba: Update rootfiles

Signed-off-by: Michael Tremer <email address hidden>

8767. By Michael Tremer <email address hidden> on 2021-04-11

Install sysctl.conf only on those architectures where needed

Signed-off-by: Michael Tremer <email address hidden>

8766. By Michael Tremer <email address hidden> on 2021-04-10

Merge remote-tracking branch 'origin/next'

8765. By Michael Tremer <email address hidden> on 2021-03-25

openssl: Update to 1.1.1k

From https://www.openssl.org/news/secadv/20210325.txt:

OpenSSL Security Advisory [25 March 2021]
=========================================

CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)
========================================================================

Severity: High

The X509_V_FLAG_X509_STRICT flag enables additional security checks of the
certificates present in a certificate chain. It is not set by default.

Starting from OpenSSL version 1.1.1h a check to disallow certificates in
the chain that have explicitly encoded elliptic curve parameters was added
as an additional strict check.

An error in the implementation of this check meant that the result of a
previous check to confirm that certificates in the chain are valid CA
certificates was overwritten. This effectively bypasses the check
that non-CA certificates must not be able to issue other certificates.

If a "purpose" has been configured then there is a subsequent opportunity
for checks that the certificate is a valid CA. All of the named "purpose"
values implemented in libcrypto perform this check. Therefore, where
a purpose is set the certificate chain will still be rejected even when the
strict flag has been used. A purpose is set by default in libssl client and
server certificate verification routines, but it can be overridden or
removed by an application.

In order to be affected, an application must explicitly set the
X509_V_FLAG_X509_STRICT verification flag and either not set a purpose
for the certificate verification or, in the case of TLS client or server
applications, override the default purpose.

OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these
versions should upgrade to OpenSSL 1.1.1k.

OpenSSL 1.0.2 is not impacted by this issue.

This issue was reported to OpenSSL on 18th March 2021 by Benjamin Kaduk
from Akamai and was discovered by Xiang Ding and others at Akamai. The fix was
developed by Tomáš Mráz.

NULL pointer deref in signature_algorithms processing (CVE-2021-3449)
=====================================================================

Severity: High

An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation
ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits
the signature_algorithms extension (where it was present in the initial
ClientHello), but includes a signature_algorithms_cert extension then a NULL
pointer dereference will result, leading to a crash and a denial of service
attack.

A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which
is the default configuration). OpenSSL TLS clients are not impacted by this
issue.

All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions
should upgrade to OpenSSL 1.1.1k.

OpenSSL 1.0.2 is not impacted by this issue.

This issue was reported to OpenSSL on 17th March 2021 by Nokia. The fix was
developed by Peter Kästle and Samuel Sapalski from Nokia.

Signed-off-by: Michael Tremer <email address hidden>

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.