From owner-cvs-doc@FreeBSD.ORG Sun Nov 12 21:13:07 2006 Return-Path: X-Original-To: cvs-doc@FreeBSD.org Delivered-To: cvs-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22F7E16A492; Sun, 12 Nov 2006 21:13:07 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from pne-smtpout1-sn2.hy.skanova.net (pne-smtpout1-sn2.hy.skanova.net [81.228.8.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id B952643D7E; Sun, 12 Nov 2006 21:12:58 +0000 (GMT) (envelope-from niclas.zeising@gmail.com) Received: from [90.224.57.146] (90.224.57.146) by pne-smtpout1-sn2.hy.skanova.net (7.2.075) id 453F8F4200364C8F; Sun, 12 Nov 2006 22:12:57 +0100 Message-ID: <45578E57.3070006@gmail.com> Date: Sun, 12 Nov 2006 22:12:55 +0100 From: Niclas Zeising User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Giorgos Keramidas References: <200611120013.kAC0D5GM097268@repoman.freebsd.org> <200611121144.28895.jkois@freebsd.org> <4556FE2A.1080501@n00b.apagnu.se> <20061112111431.GA84563@abigail.blackend.org> <20061112182751.GB834@turion.vk2pj.dyndns.org> <20061112190008.GA7008@kobe.laptop> In-Reply-To: <20061112190008.GA7008@kobe.laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-doc@FreeBSD.org, Peter Jeremy , cvs-all@FreeBSD.org, Johann Kois , doc-committers@FreeBSD.org, Marc Fonvieille Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/security chapter.sgml X-BeenThere: cvs-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the doc and www trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 21:13:07 -0000 Giorgos Keramidas wrote: > On 2006-11-13 05:27, Peter Jeremy wrote: >> On Sun, 2006-Nov-12 12:14:31 +0100, Marc Fonvieille wrote: >>> SSH is the protocol, and ssh is the application/program (so >>> or according to the >>> situation). >> To be pedantic, the application is OpenSSH. > > Well, right now, yes. But it is "a member of the family of applications > which implement the `SSH' protocol". I am not saying that this can > actually happen real soon now, but if OpenSSH doesn't work the way we > want it to work, it is possible that our SSH > in a few years will be FooSSH. > > When the 'Open' part of 'OpenSSH' is important, it is obligatory that > we mention and make it stand out (if not for any other reason, as a form > of our appreciation for the work of the OpenSSH folks). But when we > talk about the 'SSH' protocol in general, do we really have to do so? > > - Giorgos > This chapter, as far as I can tell, talks about SSH in general, as Giorgos stated. There is another chapter talking about OpenSSH in particular, and in that chapter OpenSSH is used when talking about the application. //Niclas