diff options
author | Ed Maste <emaste@FreeBSD.org> | 2022-08-19 14:39:17 +0000 |
---|---|---|
committer | Ed Maste <emaste@FreeBSD.org> | 2022-08-19 14:39:17 +0000 |
commit | 97be6fced7dbfe20d736c6aad295e18ea5fa477e (patch) | |
tree | f908f98c8f600d5d4e517d377ece9f8efed5ed6f | |
parent | bffe60ead024a1fdf4312eaec5892435a7f6b4c5 (diff) |
openssh: Remove description of VersionAddendum in upgrade doc
-rw-r--r-- | crypto/openssh/FREEBSD-upgrade | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/crypto/openssh/FREEBSD-upgrade b/crypto/openssh/FREEBSD-upgrade index 52793e84c366..f50e54edcc44 100644 --- a/crypto/openssh/FREEBSD-upgrade +++ b/crypto/openssh/FREEBSD-upgrade @@ -129,19 +129,6 @@ An overview of FreeBSD changes to OpenSSH-portable ================================================== -0) VersionAddendum - - The SSH protocol allows for a human-readable version string of up - to 40 characters to be appended to the protocol version string. - FreeBSD takes advantage of this to include a date indicating the - "patch level", so people can easily determine whether their system - is vulnerable when an OpenSSH advisory goes out. Some people, - however, dislike advertising their patch level in the protocol - handshake, so we've added a VersionAddendum configuration variable - to allow them to change or disable it. Upstream added support for - VersionAddendum on the server side, but we also support it on the - client side. - 1) Modified server-side defaults We've modified some configuration defaults in sshd: |