This issue tracks the release note for the following F26 Change:
https://fedoraproject.org/wiki/Changes/OpenSSH_Crypto_Policy
If you want to write this release note, then:
Note that sometimes, the contact people are unresponsive. Try to do your best, but if nobody gets back to you, it's not the end of the world.
Once you're done with the above, make sure to either commit the relnote to an appropriate section of the Release Notes book, or, if you're not familiar with Git, DocBook, or whatever else, just add it to this issue as a comment and let pbokoc[1] know that you're done with this one and you'd like the note included. Be sure to do this at least one day before the final release (so the limit is July 10 according to the current schedule). Also make sure to do this even for relnotes that haven't been checked by the change owner.
[0] You can do that by asking the change owner listed on the wiki page; alternatively you can infer it by checking the tracker bug (linked in Wiki) in Bugzilla and looking at its status; see bug comments for details. Ask someone on the mailing list or on IRC if you're not sure. [1] In #fedora-docs on FreeNode (UTC+1 timezone, online mostly during the day on weekdays), or pbokoc@redhat.com if you can't get a hold of me on IRC.
@jjelen Can you provide a Release Note for this change?
Metadata Update from @immanetize: - Issue assigned to immanetize
I've got this, https://pagure.io/release-notes/c/78c0cbc3b67c13d4426b613d96f8fdfef46e9cbe?branch=f26 .
Metadata Update from @immanetize: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@immanetize I would not title it "OpenSSH Crypt", but rather "OpenSSH Client". I would also add a way to overwrite the default, lets say for legacy servers (rather than opt-outing system-wide. Something like:
"You can adjust the configuration for legacy servers in your ~/.ssh/config by allowing required algorithms per host."
~/.ssh/config
Login to comment on this ticket.