https://bugzilla.redhat.com/show_bug.cgi?id=1285374

            Bug ID: 1285374
           Summary: F23 release notes don't mention that OpenSSH 7.0
                    disabled ssh-dss public keys by default
           Product: Fedora Documentation
           Version: devel
         Component: release-notes
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected], [email protected],
                    [email protected]
            Blocks: 151189 (fc-relnotes-traqr)



Fedora 22 to Fedora 23 upgrades OpenSSH from 6.9 to 7.1, but the release notes
only mention 7.1 and don't mention the default configuration changes that
happened in 7.0, such as the disabling of ssh-dss public keys that may prevent
a login to/from upgraded systems without explicit command line parameters.

https://docs.fedoraproject.org/en-US/Fedora/23/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html

Actual results:

it only links to 7.1 release notes.

"3.4.2. OpenSSH 7.1
The OpenSSH project continues to improve the security of network communication
with the release of OpenSSH 7.1. See the upstream release notes for detailed
information about this release."

Expected results:

there should be at least a link to the OpenSSH 7.0 release notes too;
possibly explicitly mentioning the disabling of public keys.

http://www.openssh.com/txt/release-7.0

"Support for ssh-dss, ssh-dss-cert-* host and user keys is disabled by default
at run-time. To temporarily enable existing host keys, use the command line
option '-oHostKeyAlgorithms=ssh-dss' and to enable existing user keys, use
'-oPubkeyAcceptedKeyTypes=ssh-dss'."


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=151189
[Bug 151189] Fedora release notes tracker bug
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
--
relnotes-content mailing list
[email protected]
http://lists.fedoraproject.org/admin/lists/[email protected]

Reply via email to