From: Jamis Buck <jgb3@...>
Date: 2004-06-14T12:37:43+09:00
Subject: Re: OpenSSL: patch

Mark Hubbart wrote:

> can't wait to see that :) I can think of several uses right off the top 
> of my head.

I'm glad I'm not the only one that wants this. It's been a pretty 
challenging project! I've wanted this for some time, and I finally 
decided that it wasn't going to happen if I just kept waiting for 
someone else to do it. :) I'm a little nervous about releasing it to the 
general public, since (as I've stressed before) cryptography is not by 
strong point, by any stretch of the imagination, and reading through the 
SSH specs has really emphasized that for me. I've sure learned a ton 
about it in the last 3 weeks, though! :)

I finished refactoring my existing code just a few minutes ago. Now I've 
got the transport layer about 80% done and a proof-of-concept 
user-authentication service written (meaning it's really only about 10% 
done). To be written: the connection service, which (when finished) will 
be the real "meat and potatoes" of Net::SSH, since that will be the 
service that allows you to execute programs (for instance) on the remote 
host. Once that's done I'll probably bundle it up and release it, with 
the caveat that it's still experimental. At that point, I would REALLY 
appreciate feedback (and patches, preferably).

Also, I'm kind of lost as to how to write test cases for something like 
this. It's hard to (for instance) force the server to send something 
unexpected without writing your own server... :( Any tips?

-- 
Jamis Buck
jgb3@email.byu.edu
http://www.jamisbuck.org/jamis

ruby -h | ruby -e 
'a=[];readlines.join.scan(/-(.)\[e|Kk(\S*)|le.l(..)e|#!(\S*)/) {|r| a << 
r.compact.first };puts "\n>#{a.join(%q/ /)}<\n\n"'