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