Bug 1281705
Summary: | Bad cipher 'blowfish' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vratislav Podzimek <vpodzime> |
Component: | openssh | Assignee: | Jakub Jelen <jjelen> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | jjelen, mattias.ellert, mgrepl, plautrba, tmraz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-23 09:08:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vratislav Podzimek
2015-11-13 08:06:50 UTC
Sorry for a late answer. I missed this bug somehow.
If you check the manual page for ssh_config(5), you will read:
> Cipher Specifies the cipher to use for encrypting the session in protocol version 1.
This explains it. This option has nothing to do in current setups and has no effect for protocol SSHv2.
From my opinion, it should rather yell about unsupported option, since SSHv1 is gone in version 7+. This is only thing we can fix. Maintaining compatible options for many years obsolete protocol is not a good idea.
(In reply to Jakub Jelen from comment #1) > Sorry for a late answer. I missed this bug somehow. > > If you check the manual page for ssh_config(5), you will read: > > > Cipher Specifies the cipher to use for encrypting the session in protocol version 1. > > This explains it. This option has nothing to do in current setups and has no > effect for protocol SSHv2. > > > From my opinion, it should rather yell about unsupported option, since SSHv1 > is gone in version 7+. This is only thing we can fix. Maintaining compatible > options for many years obsolete protocol is not a good idea. Fair enough, thanks for the explanation. |