On Wed, Apr 26, 2000 at 12:09:12PM -0400, Blue Lang wrote:
> > Yes, most lists are user to user. That's how Open Source works. Yah, I
> > know SSH isn't exactly in the Open Source development model, but it isn't
> > that Micro company either.
>
> I certainly don't mean to slight the helpful users who are on this list in
> my next comments - they are directly only at the 'official' ssh
> maintainers.
So you know, we try to be out there as much as possible. You'll see that
several people respond to questions on this list: myself, Tatu, and Sami
Lehtinen whenever we can. I try to stay as active as possible because I
co-maintain the Secure Shell FAQ with Steve Acheson.
However, this is non-vendor specific mailing list. People can ask questions
about SSH Secure Shell, Van Dyke clients (SecureCRT and SecureFX), F-Secure
products, OpenSSH, lsh, and any other of the other many free implementations
available.
> I'm on a lot of lists. SSH stands out as being the least responsive of
> them. If I knew more about it, I would offer help to more people, but I'm
> really just an admin/hacker type with some vague background in C. SSH is
> not free software - if it were, I would be able to just hack it at will
> and post my changes to a different page.
Actually, the non-commercial release is free software. You are more than
welcome to hack at the code and post patches wherever possible. Many people
have done so, including:
Jean's patch for SSH1 to include SecurID support
ftp.parc.xerox.com/pub/jean/sshsdi
Per Erik's ftpsshd for SSH1
http://www.docs.uu.se/~pem/hacks/
Jim's SSH patch repository
http://www.ncsa.uiuc.edu/General/CC/ssh/patch_repository/
We also do receive patches on occasion, and we test and incorporate
them wherever possible. We do provide a non-commercial release of the
SSH Secure Shell code, which is the exact same thing as the commercial
release.
> And I know that there are people from ssh.org on this list, and I know
> that there are a lot of questions that have gone unanswered, and it makes
> me sad.
Actually, many people do get responded to, just the entire list is not
always copied. By default, the response only goes to the person responding--
not the entire list.
> If they charge a fee for use, and aren't willing to 'help' in the OSS
> spirit, then they might as well be mickeysoft, for all the good they do
> me.
We do not charge a fee for non-commercial use. If you are using SSH Secure
Shell for unversity and personal use, you are more than welcome to use the
product as you see fit.
If you are using SSH Secure Shell in a commercial environment, it should
be licensed through us and that entitles you to commercial support. However,
this list is not for commercial SSH Secure Shell users: it's for anyone who
wants to discuss anything about Secure Shell and its numerous implementations.
-Anne
________________________________________________________________________
Anne Carasik, Principal Consultant | Any two consenting adults can rub
SSH Communications Security, Inc. | two primes together to create
Email: [EMAIL PROTECTED] | a public keypair" - R. Thayer
------------------------------------------------------------------------
My opinions on my own. My employer doesn't want them.
