Bug 798341 - Users unable to connect to port 22 with anything other than openssh on windows
Summary: Users unable to connect to port 22 with anything other than openssh on windows
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Mike McGrath
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 17:05 UTC by Nam Duong
Modified: 2015-05-14 22:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-27 16:11:59 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nam Duong 2012-02-28 17:05:51 UTC 
Description of problem:
One of our users raised the problem that none of the following clients can connect through ssh:
  - sftp
  - WinSCP
  - Putty

I also noticed the same issue with macfusion.

When diving into WinSCP and Putty (more common on Windows than cmdline openssh), I noticed that it didn't support the same ciphers as openSSH.  There is a tool that can be used to generate ssh keys called puttygen.  Tried 2 different approaches that also didn't work:
  - convert the keys generated by openssh
  - create new keys and post them to the domain (via control panel)

Please note that there are 3 users so far, 1 on Mac and 2 on windows whom are having problems.  The workaround is to use command line ssh and scp...
Comment 1 Rob Millner 2012-02-28 22:12:47 UTC 
The issue with putty may be related to a key format compatibility issue.

http://stackoverflow.com/questions/2224066/how-to-convert-ssh-keypairs-generated-using-puttygenwindows-into-key-pairs-use
Comment 2 Mike McGrath 2012-08-27 16:11:59 UTC 
Nod, this isn't a bug with OpenSSH/OpenShift, it's a bug with putty and some of the other windows based ssh clients.  They use a different key format.

Nam, can you create an FAQ that links to Rob's URL (or just re-write the FAQ with similar information.
Note You need to log in before you can comment on or make changes to this bug.