From owner-freebsd-doc Thu Apr 13 20: 8:50 2000 Delivered-To: freebsd-doc@freebsd.org Received: from berlin.atlantic.net (berlin.atlantic.net [209.208.0.20]) by hub.freebsd.org (Postfix) with ESMTP id 3652837B57D for ; Thu, 13 Apr 2000 20:08:47 -0700 (PDT) (envelope-from bobj@atlantic.net) Received: from mail.atlantic.net (mail.atlantic.net [209.208.0.71]) by berlin.atlantic.net (8.9.3/8.9.3) with ESMTP id XAA05461 for ; Thu, 13 Apr 2000 23:12:21 -0400 Received: from bsd.cisi.com (ocalflifanb-as-1-r1-ip-99.atlantic.net [209.208.28.99]) by mail.atlantic.net (8.9.3/8.9.3) with ESMTP id XAA30699 for ; Thu, 13 Apr 2000 23:08:43 -0400 Received: from nancy.cisi.com (nancy.cisi.com [192.168.0.131]) by bsd.cisi.com (8.9.3/8.9.3) with SMTP id XAA03021 for ; Thu, 13 Apr 2000 23:07:33 -0400 (EDT) (envelope-from bobj@atlantic.net) Message-Id: <3.0.6.32.20000413230659.00a01560@rio.atlantic.net> X-Sender: bobj@rio.atlantic.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 13 Apr 2000 23:06:59 -0400 To: doc@freebsd.org From: Bob Johnson Subject: SSH not in Handbook table of contents Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got an observation with no clear suggestion of what should be done about it: I was looking for information on using ssh today, and noticed that the FreeBSD Handbook doesn't have ssh listed in the table of contents. Other security goodies have their own sections, but all of the ssh information is found in the general "Securing FreeBSD" section. Even S/Key, which, like ssh, is included by default, has its own section. This leads to two observations/suggestions: 1) It's hard to find the information on ssh because it doesn't show up in the TOC. 2) I think a separate section on both how to set up and how to use SSH would be nice. Things like how to set up ftp via ssh would be good. I know that information is elsewhere, but it's awful nice to have one place to go for all the good info... I'm not sure what to do about (1) that doesn't require also fixing (2), and that would probably require rewriting the "Securing FreeBSD" section as well. I haven't even had time to post a list of typos I made about 10 days ago, so I ain't volunteering for nuttin' at the moment. Sorry. -- Bob +-------------------------------------------------------- | Bob Johnson | bobj@atlantic.net +-------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message