Bug 88329 - RFE openssh daemon enables protocol 1 by default
RFE openssh daemon enables protocol 1 by default
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: openssh (Show other bugs)
rawhide
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Brian Brock
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-08 18:42 EDT by Kevin J. Miller
Modified: 2007-11-30 17:10 EST (History)
4 users (show)

See Also:
Fixed In Version: openssh-3.9p1-10
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-08 10:38:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Kevin J. Miller 2003-04-08 18:42:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
The file /etc/ssh/sshd_config has both protocols 1 and 2 of ssh enabled by
default.  Protocol 1 has known security problems, and should be disabled by default.

Version-Release number of selected component (if applicable):
openssh-server-3.5p1-6

How reproducible:
Always

Steps to Reproduce:
1.  I can log in with a protocol 1 client.
    

Additional info:
Comment 1 Nathan G. Grennan 2003-04-09 23:48:39 EDT
I agree, I have been having to disable it manually on all the machines I
administrate. I have even found putty using ssh1 by default. So this just isn't
a case of when people use ssh1 on purpose.
Comment 2 Mark J. Cox (Product Security) 2003-06-02 07:48:46 EDT
Whilst protocol version 1 has some 'known security issues' in general these did
not affect OpenSSH.  For example looking at
http://www.f-secure.com/support/technical/ssh/ssh1_vulnerabilities.shtml each of
these issues does not affect OpenSSH, and http://www.openssh.com/goals.html
gives you some more details.
Comment 3 Tomas Mraz 2005-02-04 09:14:56 EST
We should consider this again as most clients now support ssh v2.

Note You need to log in before you can comment on or make changes to this bug.