diff options
Diffstat (limited to 'debian/NEWS')
-rw-r--r-- | debian/NEWS | 261 |
1 files changed, 261 insertions, 0 deletions
diff --git a/debian/NEWS b/debian/NEWS new file mode 100644 index 000000000..c8d01545f --- /dev/null +++ b/debian/NEWS | |||
@@ -0,0 +1,261 @@ | |||
1 | openssh (1:8.0p1-1) unstable; urgency=medium | ||
2 | |||
3 | OpenSSH 8.0 includes a number of changes that may affect existing | ||
4 | configurations: | ||
5 | |||
6 | * sshd(8): Remove support for obsolete "host/port" syntax. | ||
7 | Slash-separated host/port was added in 2001 as an alternative to | ||
8 | host:port syntax for the benefit of IPv6 users. These days there are | ||
9 | established standards for this like [::1]:22 and the slash syntax is | ||
10 | easily mistaken for CIDR notation, which OpenSSH supports for some | ||
11 | things. Remove the slash notation from ListenAddress and PermitOpen. | ||
12 | |||
13 | -- Colin Watson <cjwatson@debian.org> Wed, 05 Jun 2019 07:09:47 +0100 | ||
14 | |||
15 | openssh (1:7.9p1-1) unstable; urgency=medium | ||
16 | |||
17 | OpenSSH 7.9 includes a number of changes that may affect existing | ||
18 | configurations: | ||
19 | |||
20 | * ssh(1), sshd(8): the setting of the new CASignatureAlgorithms option | ||
21 | bans the use of DSA keys as certificate authorities. | ||
22 | * sshd(8): the authentication success/failure log message has changed | ||
23 | format slightly. It now includes the certificate fingerprint | ||
24 | (previously it included only key ID and CA key fingerprint). | ||
25 | |||
26 | -- Colin Watson <cjwatson@debian.org> Sun, 21 Oct 2018 10:39:24 +0100 | ||
27 | |||
28 | openssh (1:7.8p1-1) unstable; urgency=medium | ||
29 | |||
30 | OpenSSH 7.8 includes a number of changes that may affect existing | ||
31 | configurations: | ||
32 | |||
33 | * ssh-keygen(1): Write OpenSSH format private keys by default instead of | ||
34 | using OpenSSL's PEM format. The OpenSSH format, supported in OpenSSH | ||
35 | releases since 2014 and described in the PROTOCOL.key file in the | ||
36 | source distribution, offers substantially better protection against | ||
37 | offline password guessing and supports key comments in private keys. | ||
38 | If necessary, it is possible to write old PEM-style keys by adding "-m | ||
39 | PEM" to ssh-keygen's arguments when generating or updating a key. | ||
40 | * sshd(8): Remove internal support for S/Key multiple factor | ||
41 | authentication. S/Key may still be used via PAM or BSD auth. | ||
42 | * ssh(1): Remove vestigial support for running ssh(1) as setuid. This | ||
43 | used to be required for hostbased authentication and the (long gone) | ||
44 | rhosts-style authentication, but has not been necessary for a long | ||
45 | time. Attempting to execute ssh as a setuid binary, or with uid != | ||
46 | effective uid will now yield a fatal error at runtime. | ||
47 | * sshd(8): The semantics of PubkeyAcceptedKeyTypes and the similar | ||
48 | HostbasedAcceptedKeyTypes options have changed. These now specify | ||
49 | signature algorithms that are accepted for their respective | ||
50 | authentication mechanism, where previously they specified accepted key | ||
51 | types. This distinction matters when using the RSA/SHA2 signature | ||
52 | algorithms "rsa-sha2-256", "rsa-sha2-512" and their certificate | ||
53 | counterparts. Configurations that override these options but omit | ||
54 | these algorithm names may cause unexpected authentication failures (no | ||
55 | action is required for configurations that accept the default for these | ||
56 | options). | ||
57 | * sshd(8): The precedence of session environment variables has changed. | ||
58 | ~/.ssh/environment and environment="..." options in authorized_keys | ||
59 | files can no longer override SSH_* variables set implicitly by sshd. | ||
60 | * ssh(1)/sshd(8): The default IPQoS used by ssh/sshd has changed. They | ||
61 | will now use DSCP AF21 for interactive traffic and CS1 for bulk. For a | ||
62 | detailed rationale, please see the commit message: | ||
63 | https://cvsweb.openbsd.org/src/usr.bin/ssh/readconf.c#rev1.284 | ||
64 | |||
65 | -- Colin Watson <cjwatson@debian.org> Thu, 30 Aug 2018 15:35:27 +0100 | ||
66 | |||
67 | openssh (1:7.6p1-1) unstable; urgency=medium | ||
68 | |||
69 | OpenSSH 7.6 includes a number of changes that may affect existing | ||
70 | configurations: | ||
71 | |||
72 | * ssh(1): Delete SSH protocol version 1 support, associated configuration | ||
73 | options and documentation. | ||
74 | * ssh(1)/sshd(8): Remove support for the hmac-ripemd160 MAC. | ||
75 | * ssh(1)/sshd(8): Remove support for the arcfour, blowfish and CAST | ||
76 | ciphers. | ||
77 | * Refuse RSA keys <1024 bits in length and improve reporting for keys | ||
78 | that do not meet this requirement. | ||
79 | * ssh(1): Do not offer CBC ciphers by default. | ||
80 | |||
81 | -- Colin Watson <cjwatson@debian.org> Fri, 06 Oct 2017 12:36:48 +0100 | ||
82 | |||
83 | openssh (1:7.5p1-1) experimental; urgency=medium | ||
84 | |||
85 | OpenSSH 7.5 includes a number of changes that may affect existing | ||
86 | configurations: | ||
87 | |||
88 | * This release deprecates the sshd_config UsePrivilegeSeparation option, | ||
89 | thereby making privilege separation mandatory. | ||
90 | |||
91 | * The format of several log messages emitted by the packet code has | ||
92 | changed to include additional information about the user and their | ||
93 | authentication state. Software that monitors ssh/sshd logs may need to | ||
94 | account for these changes. For example: | ||
95 | |||
96 | Connection closed by user x 1.1.1.1 port 1234 [preauth] | ||
97 | Connection closed by authenticating user x 10.1.1.1 port 1234 [preauth] | ||
98 | Connection closed by invalid user x 1.1.1.1 port 1234 [preauth] | ||
99 | |||
100 | Affected messages include connection closure, timeout, remote | ||
101 | disconnection, negotiation failure and some other fatal messages | ||
102 | generated by the packet code. | ||
103 | |||
104 | -- Colin Watson <cjwatson@debian.org> Sun, 02 Apr 2017 02:58:01 +0100 | ||
105 | |||
106 | openssh (1:7.4p1-7) unstable; urgency=medium | ||
107 | |||
108 | This version restores the default for AuthorizedKeysFile to search both | ||
109 | ~/.ssh/authorized_keys and ~/.ssh/authorized_keys2, as was the case in | ||
110 | Debian configurations before 1:7.4p1-1. Upstream intends to phase out | ||
111 | searching ~/.ssh/authorized_keys2 by default, so you should ensure that | ||
112 | you are only using ~/.ssh/authorized_keys, at least for critical | ||
113 | administrative access; do not assume that the current default will remain | ||
114 | in place forever. | ||
115 | |||
116 | -- Colin Watson <cjwatson@debian.org> Sun, 05 Mar 2017 02:12:42 +0000 | ||
117 | |||
118 | openssh (1:7.4p1-1) unstable; urgency=medium | ||
119 | |||
120 | OpenSSH 7.4 includes a number of changes that may affect existing | ||
121 | configurations: | ||
122 | |||
123 | * ssh(1): Remove 3des-cbc from the client's default proposal. 64-bit | ||
124 | block ciphers are not safe in 2016 and we don't want to wait until | ||
125 | attacks like SWEET32 are extended to SSH. As 3des-cbc was the only | ||
126 | mandatory cipher in the SSH RFCs, this may cause problems connecting to | ||
127 | older devices using the default configuration, but it's highly likely | ||
128 | that such devices already need explicit configuration for key exchange | ||
129 | and hostkey algorithms already anyway. | ||
130 | * sshd(8): Remove support for pre-authentication compression. Doing | ||
131 | compression early in the protocol probably seemed reasonable in the | ||
132 | 1990s, but today it's clearly a bad idea in terms of both cryptography | ||
133 | (cf. multiple compression oracle attacks in TLS) and attack surface. | ||
134 | Pre-auth compression support has been disabled by default for >10 | ||
135 | years. Support remains in the client. | ||
136 | * ssh-agent will refuse to load PKCS#11 modules outside a whitelist of | ||
137 | trusted paths by default. The path whitelist may be specified at | ||
138 | run-time. | ||
139 | * sshd(8): When a forced-command appears in both a certificate and an | ||
140 | authorized keys/principals command= restriction, sshd will now refuse | ||
141 | to accept the certificate unless they are identical. The previous | ||
142 | (documented) behaviour of having the certificate forced-command | ||
143 | override the other could be a bit confusing and error-prone. | ||
144 | * sshd(8): Remove the UseLogin configuration directive and support for | ||
145 | having /bin/login manage login sessions. | ||
146 | |||
147 | The unprivileged sshd process that deals with pre-authentication network | ||
148 | traffic is now subject to additional sandboxing restrictions by default: | ||
149 | that is, the default sshd_config now sets UsePrivilegeSeparation to | ||
150 | "sandbox" rather than "yes". This has been the case upstream for a while, | ||
151 | but until now the Debian configuration diverged unnecessarily. | ||
152 | |||
153 | -- Colin Watson <cjwatson@debian.org> Tue, 27 Dec 2016 18:01:46 +0000 | ||
154 | |||
155 | openssh (1:7.2p1-1) unstable; urgency=medium | ||
156 | |||
157 | OpenSSH 7.2 disables a number of legacy cryptographic algorithms by | ||
158 | default in ssh: | ||
159 | |||
160 | * Several ciphers blowfish-cbc, cast128-cbc, all arcfour variants and the | ||
161 | rijndael-cbc aliases for AES. | ||
162 | * MD5-based and truncated HMAC algorithms. | ||
163 | |||
164 | These algorithms are already disabled by default in sshd. | ||
165 | |||
166 | -- Colin Watson <cjwatson@debian.org> Tue, 08 Mar 2016 11:47:20 +0000 | ||
167 | |||
168 | openssh (1:7.1p1-2) unstable; urgency=medium | ||
169 | |||
170 | OpenSSH 7.0 disables several pieces of weak, legacy, and/or unsafe | ||
171 | cryptography. | ||
172 | |||
173 | * Support for the legacy SSH version 1 protocol is disabled by default at | ||
174 | compile time. Note that this also means that the Cipher keyword in | ||
175 | ssh_config(5) is effectively no longer usable; use Ciphers instead for | ||
176 | protocol 2. The openssh-client-ssh1 package includes "ssh1", "scp1", | ||
177 | and "ssh-keygen1" binaries which you can use if you have no alternative | ||
178 | way to connect to an outdated SSH1-only server; please contact the | ||
179 | server administrator or system vendor in such cases and ask them to | ||
180 | upgrade. | ||
181 | * Support for the 1024-bit diffie-hellman-group1-sha1 key exchange is | ||
182 | disabled by default at run-time. It may be re-enabled using the | ||
183 | instructions at http://www.openssh.com/legacy.html | ||
184 | * Support for ssh-dss, ssh-dss-cert-* host and user keys is disabled by | ||
185 | default at run-time. These may be re-enabled using the instructions at | ||
186 | http://www.openssh.com/legacy.html | ||
187 | * Support for the legacy v00 cert format has been removed. | ||
188 | |||
189 | Future releases will retire more legacy cryptography, including: | ||
190 | |||
191 | * Refusing all RSA keys smaller than 1024 bits (the current minimum is | ||
192 | 768 bits). | ||
193 | * Several ciphers will be disabled by default: blowfish-cbc, cast128-cbc, | ||
194 | all arcfour variants, and the rijndael-cbc aliases for AES. | ||
195 | * MD5-based HMAC algorithms will be disabled by default. | ||
196 | |||
197 | -- Colin Watson <cjwatson@debian.org> Tue, 08 Dec 2015 15:33:08 +0000 | ||
198 | |||
199 | openssh (1:6.9p1-1) unstable; urgency=medium | ||
200 | |||
201 | UseDNS now defaults to 'no'. Configurations that match against the client | ||
202 | host name (via sshd_config or authorized_keys) may need to re-enable it or | ||
203 | convert to matching against addresses. | ||
204 | |||
205 | -- Colin Watson <cjwatson@debian.org> Thu, 20 Aug 2015 10:38:58 +0100 | ||
206 | |||
207 | openssh (1:6.7p1-5) unstable; urgency=medium | ||
208 | |||
209 | openssh-server 1:6.7p1-4 changed the default setting of AcceptEnv to list | ||
210 | a number of specific LC_FOO variables rather than the wildcard LC_*. I | ||
211 | have since been persuaded that this was a bad idea and have reverted it, | ||
212 | but it is difficult to automatically undo the change to | ||
213 | /etc/ssh/sshd_config without compounding the problem (that of modifying | ||
214 | configuration that some users did not want to be modified) further. Most | ||
215 | users who upgraded via version 1:6.7p1-4 should restore the previous value | ||
216 | of "AcceptEnv LANG LC_*" in /etc/ssh/sshd_config. | ||
217 | |||
218 | -- Colin Watson <cjwatson@debian.org> Sun, 22 Mar 2015 23:09:32 +0000 | ||
219 | |||
220 | openssh (1:5.4p1-2) unstable; urgency=low | ||
221 | |||
222 | Smartcard support is now available using PKCS#11 tokens. If you were | ||
223 | previously using an unofficial build of Debian's OpenSSH package with | ||
224 | OpenSC-based smartcard support added, then note that commands like | ||
225 | 'ssh-add -s 0' will no longer work; you need to use 'ssh-add -s | ||
226 | /usr/lib/opensc-pkcs11.so' instead. | ||
227 | |||
228 | -- Colin Watson <cjwatson@debian.org> Sat, 10 Apr 2010 01:08:59 +0100 | ||
229 | |||
230 | openssh (1:3.8.1p1-9) experimental; urgency=low | ||
231 | |||
232 | The ssh package has been split into openssh-client and openssh-server. If | ||
233 | you had previously requested that the sshd server should not be run, then | ||
234 | that request will still be honoured. However, the recommended approach is | ||
235 | now to remove the openssh-server package if you do not want to run sshd. | ||
236 | You can remove the old /etc/ssh/sshd_not_to_be_run marker file after doing | ||
237 | that. | ||
238 | |||
239 | -- Colin Watson <cjwatson@debian.org> Mon, 2 Aug 2004 20:48:54 +0100 | ||
240 | |||
241 | openssh (1:3.5p1-1) unstable; urgency=low | ||
242 | |||
243 | This version of OpenSSH disables the environment option for public keys by | ||
244 | default, in order to avoid certain attacks (for example, LD_PRELOAD). If | ||
245 | you are using this option in an authorized_keys file, beware that the keys | ||
246 | in question will no longer work until the option is removed. | ||
247 | |||
248 | To re-enable this option, set "PermitUserEnvironment yes" in | ||
249 | /etc/ssh/sshd_config after the upgrade is complete, taking note of the | ||
250 | warning in the sshd_config(5) manual page. | ||
251 | |||
252 | -- Colin Watson <cjwatson@debian.org> Sat, 26 Oct 2002 19:41:51 +0100 | ||
253 | |||
254 | openssh (1:3.0.1p1-1) unstable; urgency=high | ||
255 | |||
256 | As of version 3, OpenSSH no longer uses separate files for ssh1 and ssh2 | ||
257 | keys. This means the authorized_keys2 and known_hosts2 files are no longer | ||
258 | needed. They will still be read in order to maintain backward | ||
259 | compatibility. | ||
260 | |||
261 | -- Matthew Vernon <matthew@debian.org> Thu, 28 Nov 2001 17:43:01 +0000 | ||