From: eli-schwartz <eli-schwartz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [TESTING] OpenSSH 8.2
Date: Mon, 17 Feb 2020 02:34:15 +0100 [thread overview]
Message-ID: <20200217013415.FL5rGIlDbCPjgYk_XPJE9SeLqSDRABnm2eqEnDo2E9c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19131@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
New comment by eli-schwartz on void-packages repository
https://github.com/void-linux/void-packages/pull/19131#issuecomment-586783089
Comment:
Just want to mention, in case you haven't noticed...
https://lists.archlinux.org/pipermail/arch-dev-public/2020-February/029865.html
https://bugs.archlinux.org/task/65517
https://bugs.gentoo.org/709748
You are going to want to make sure users are warned to restart sshd after the update, or they won't be able to successfully connect to it.
next prev parent reply other threads:[~2020-02-17 1:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19131@inbox.vuxu.org>
2020-02-14 12:44 ` [WIP] " voidlinux-github
2020-02-14 13:02 ` voidlinux-github
2020-02-14 16:15 ` leahneukirchen
2020-02-17 1:34 ` eli-schwartz [this message]
2020-02-17 10:12 ` [TESTING] " leahneukirchen
2020-02-17 10:14 ` leahneukirchen
2020-02-17 10:59 ` Vaelatern
2020-02-17 11:59 ` leahneukirchen
2020-02-18 21:18 ` jnbr
2020-02-19 12:24 ` leahneukirchen
2020-02-20 16:01 ` [PR PATCH] [Merged]: " leahneukirchen
2020-02-20 18:26 ` ailiop-git
2020-02-20 18:58 ` leahneukirchen
2020-02-25 13:47 ` leahneukirchen
2020-02-25 14:29 ` Vaelatern
2020-02-25 18:25 ` the-maldridge
2020-02-25 18:47 ` ailiop-git
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=20200217013415.FL5rGIlDbCPjgYk_XPJE9SeLqSDRABnm2eqEnDo2E9c@z \
--to=eli-schwartz@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).