>From: Qv6 <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: #define failure opportunity
>Date: Mon, 28 Nov 2005 18:35:24 -0600
...
>Intersting news.
>
>I once worked for a major Telecom firm that used a commercial
>implementation of ssh. I was curious and I asked one of the other
>techies why pay for ssh when openssh is available. "Because we can
>go to the company for support" was his answer.
>
>I couldn't help but wonder what type of issues people encounter
>while using openssh. Aside from the usuall software bugs, has there
>really been any major problems with openssh that the community has
>not fixed promptly?
I'm reminded of the following quote I saved -- can't remember where
I found it:
Open source code is not guaranteed nor does it come with a warranty.
-- the Alexis de Tocqueville Institute
I guess that's in contrast to proprietary software, which comes with
a money-back guarantee, and free on-site repairs if any bugs are
found.
-- Rary
I certainly couldn't provide the services I currently support
without a *lot* of open source software running on OpenBSD. Well,
not without it costing a great deal of money.
