public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patches for Core Update 143
Date: Mon, 23 Mar 2020 19:58:37 +0100	[thread overview]
Message-ID: <87a8901bc6b52f10edc3be871b04deff6d234609.camel@ipfire.org> (raw)
In-Reply-To: <217bd496-6c4e-d0ca-a540-adf1140c373e@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

Hello Arne,

I also want to point you to the following unmerged patch:

https://patchwork.ipfire.org/patch/2732/

Thanks in advance,

-Stefan
> Hello Arne,
> 
> I do not want to appear utterly inquisitive, but may I ask you to
> have a look
> at these patches:
> 
> (a) mail.cgi: add support for implicit TLS usage
> 	-> https://patchwork.ipfire.org/patch/2748/
> 	-> https://patchwork.ipfire.org/patch/2749/
> (b) coreutils: update to 8.31 
> 	-> https://patchwork.ipfire.org/patch/2746/
> 	-> https://patchwork.ipfire.org/patch/2747/
> (c) dma: update to 0.12
> 	-> https://patchwork.ipfire.org/patch/2743/
> (d) avoid emitting VPN traffic to the internet if the IPS crashed
> 	-> https://patchwork.ipfire.org/patch/2727/
> (e) sshd_config: Do not set defaults explicitly
> 	-> https://patchwork.ipfire.org/patch/2711/
> 	-> https://patchwork.ipfire.org/patch/2712/
> (f) sysctl.conf: Turn on hard- and symlink protection
> 	-> https://patchwork.ipfire.org/patch/2720/
> 
> I will care about OpenSSH 8.2p1 with glibc 2.31 this afternoon.
> 
> Thanks, and best regards,
> Peter Müller


      parent reply	other threads:[~2020-03-23 18:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 14:59 Peter Müller
2020-03-23 16:31 ` Michael Tremer
2020-03-23 18:58 ` Stefan Schantl [this message]

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=87a8901bc6b52f10edc3be871b04deff6d234609.camel@ipfire.org \
    --to=stefan.schantl@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