From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Pending patches for IPFire 2.x and 3.x
Date: Wed, 19 Feb 2020 19:22:00 +0000 [thread overview]
Message-ID: <d870653e-f664-a4b4-f87f-6b7e7727143a@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
Hello *,
since a couple of things already landed in Core Update 142, I took this
as an opportunity to clean up my patches at https://patchwork.ipfire.org/
(sorry for the delay).
As a side note, these patches or patch series are currently ready for IPFire 2.x :
- unbound.conf: Do not set defaults explicitly (https://patchwork.ipfire.org/patch/2710/)
- [1/2] sshd_config: Do not set defaults explicitly (https://patchwork.ipfire.org/project/ipfire/list/?series=1018)
- sysctl.conf: Turn on hard- and symlink protection (https://patchwork.ipfire.org/patch/2720/)
- avoid emitting VPN traffic to the internet if the IPS crashed (https://patchwork.ipfire.org/patch/2727/)
- dma: update to 0.12 (https://patchwork.ipfire.org/patch/2743/)
- Tor: update to 0.4.2.6 (https://patchwork.ipfire.org/patch/2744/)
- [v2,1/2] coreutils: update to 8.31 (https://patchwork.ipfire.org/project/ipfire/list/?series=1045)
- [v2,1/2] mail.cgi: add support for implicit TLS usage (https://patchwork.ipfire.org/project/ipfire/list/?series=1046)
strongSwan 5.8.2 is currently building here as well as some minor package updates
such as hwdata. Patches will be handed in as soon as possible.
Regarding IPFire 3.x, this patch is also ready:
- update ca-certificates CA bundle (https://patchwork.ipfire.org/patch/2618/)
If anyone was up to these already, please ignore the noise. :-) I just wanted
to avoid some patches being deferred due to closed merge windows...
Thanks, and best regards,
Peter Müller
reply other threads:[~2020-02-19 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d870653e-f664-a4b4-f87f-6b7e7727143a@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox