Path:
news1.ucsd.edu!ihnp4.ucsd.edu!munnari.OZ.AU!news.ecn.uoknor.edu!solace!xinit!fci-se!fci!news.maxwell.syr.edu!news.algonet.se!newsfeed1.funet.fi!130.233.40.178.MISMATCH!news.cs.hut.fi!news.cs.hut.fi-mailgw
From: Tadayoshi.Kohno@Colorado.EDU (Tadayoshi Kohno)
Newsgroups: comp.security.ssh
Subject: SSH v2.0; Windows client for v1.5
Date: 19 Dec 1997 00:33:51 -0000
Organization: news.cs.hut.fi mail2news gateway
Lines: 67
Distribution: world
Message-ID: <199712181951.MAA25277@taussky.cs.colorado.edu>
NNTP-Posting-Host: nukkekoti.cs.hut.fi
Xref: news1.ucsd.edu comp.security.ssh:2787

Hello.

I was wondering if someone could point me to any resources that
might explain the motivation for the development of ssh version 2.0?
It looks like the new protocol is very nice, but it also appears
to be quite different for version 1.5.  I tried to find some
archive about the development, but had little success.

The reason I ask this is that I have just implemented an ssh v1.5
client for windows 95 and nt as a final project for one of my classes
(using a draft for v1.5 that expired in May of 96).

Furthermore, I developed the ssh-protocol level routines in such
a way that they are completely separate from the interface.  What
I am hoping to do is eventually create a nice, platform independent
library for ssh routines that can support v2.0 as well as 1.5.

I know that will mean a lot more coding, but I think it will be fun
(plus I heard that, for SSH to become a standard, they need two
independently implemented version to test against each other ... I don't
know if that's true or not).

[I realize there is no real need for a library, but because of the 
modularity, it is not hard to have multiple ssh connections open
within the same program.  Using this fact, I am planning on writing
an interactive Windows secure copy program that can traverse the
filesystem via one connection, and then do the filecopy over another
connection..   I haven't thought that one through to its entirety,
but, basically, that is something that can be done through a general
ssh-library]

And now for a slight commercial:  The current version of my program
(which I call WinSSH for lack of a better name -- I had thought
of SuSHi, but my friends voted that down) supports password
and rsa authentication and des, 3des, and idea encryption. The interface
has has copy and paste and save-able configurations and the likes.
VT100 emulation is horrible.  This was also my first windows program,
so someday I would like to redo the interface using the knowledge
that I gained in the first implementation.

I use Eric Young's SSLeay encryption libraries, so should not have
any exportation problems. His libraries are very robust and portable,
which is a definite plus.  Anyone who compiles my program, however,
will need to ftp a copy of SSLeay-0.8.1 themselves.

I haven't really made my code available to the general public yet,
so this letter also serves as a query of interest.  I'd like
to know if people are interested in playing with it, but it is in
a pre-alpha stage and I don't want too many copies of this version
floating around when I release a better version.  My main task right
now is getting VT100 emulation working.  I am writing this letter using
vi over my WinSSH program, but it is slow.   I hope to get vt100 stuff
done soon so I can return my focus to creating a more robust
ssh-library (with compression, ...).

Anyway, sorry for such a long letter, and thanks for any info
about the motivation for version 2.0 and for any interest in WinSSH.

Oh, and another group wrote a version of SSHv1.5 in Java that currently
supports password authentication and idea encryption.  (they are
also planning on continuing their work next semester).

Thanks a bunch,

Yoshi Kohno
University of Colorado at Boulder