1 |
On 2/19/20 11:32 PM, Patrick McLean wrote: |
2 |
> Title: OpenSSH 8.2_p1 running sshd breakage |
3 |
> Author: Patrick McLean <chutzpah@g.o> |
4 |
> Posted: 2020-02-21 |
5 |
> Revision: 1 |
6 |
> News-Item-Format: 2.0 |
7 |
> Display-If-Installed: <net-misc/openssh-8.2 |
8 |
> |
9 |
> If sshd is running, and a system is upgraded from <net-misc/openssh-8.2_p1 |
10 |
> to >=net-misc/openssh-8.2_p1, any new ssh connection will fail until sshd is |
11 |
> restarted. |
12 |
> |
13 |
> Before restarting sshd, it is *strongly* recommended that you test your |
14 |
> configuraton with the following command (as root): |
15 |
> sshd -t |
16 |
> |
17 |
> If your system is booted with openrc, use this command (as root) |
18 |
|
19 |
double space (inconsistent with similar sentence below) |
20 |
|
21 |
|
22 |
> to restart sshd: |
23 |
> rc-service sshd --nodeps restart |
24 |
> |
25 |
> If your system is booted with systemd, use this command (as root) |
26 |
> to restart sshd: |
27 |
> systemctl restart sshd |
28 |
> |
29 |
> If you are using systemd socket activation for sshd, then no action is |
30 |
> required. |
31 |
> |
32 |
> WARNING: On systemd booted machines with PAM disabled, this command |
33 |
> will terminate all currently open ssh connections. It is *strongly* |
34 |
> recommended that you validate your configuration before restarting |
35 |
> sshd. |
36 |
> |
37 |
This is pretty much just nitpicking, but |
38 |
|
39 |
https://www.gentoo.org/glep/glep-0042.html#news-item-body |
40 |
|
41 |
"The text body should be wrapped at 72 characters. No fancy formatting |
42 |
or tab characters should be used — the news item may be being displayed |
43 |
directly to a terminal. Paragraphs should be separated by a blank line." |
44 |
|
45 |
The 72 char limit breaks 4 times. |
46 |
|
47 |
|
48 |
LGTM. |
49 |
|
50 |
|
51 |
-- juippis |