From owner-freebsd-security Wed Mar 27 11:36:43 2002 Delivered-To: freebsd-security@freebsd.org Received: from va.cs.wm.edu (va.cs.wm.edu [128.239.2.31]) by hub.freebsd.org (Postfix) with ESMTP id 42F0037B404 for ; Wed, 27 Mar 2002 11:36:34 -0800 (PST) Received: from dali.cs.wm.edu (dali [128.239.26.26]) by va.cs.wm.edu (8.11.4/8.9.1) with ESMTP id g2RJaFb05658 for ; Wed, 27 Mar 2002 14:36:15 -0500 (EST) Received: (from zvezdan@localhost) by dali.cs.wm.edu (8.11.6/8.9.1) id g2RJaOY23460 for freebsd-security@FreeBSD.ORG; Wed, 27 Mar 2002 14:36:24 -0500 Date: Wed, 27 Mar 2002 14:36:24 -0500 From: Zvezdan Petkovic To: freebsd-security@FreeBSD.ORG Subject: Re: It's time for those 2048-, 3072-, and 4096-bit keys? Message-ID: <20020327143624.B23316@dali.cs.wm.edu> Mail-Followup-To: freebsd-security@FreeBSD.ORG References: <20020326185714.F22539@mail.webmonster.de> <20020326182003.F15545-100000@patrocles.silby.com> <20020326181634.A919@lothlorien.tangledhelix.net> <20020327074236.B86929@blackhelicopters.org> <20020327110100.6d638389.darklogik@pittgoth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020327110100.6d638389.darklogik@pittgoth.com>; from darklogik@pittgoth.com on Wed, Mar 27, 2002 at 11:01:00AM -0500 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Mar 27, 2002 at 11:01:00AM -0500, Tom Rhodes wrote: > > How about a nice addition to the ssh manual pages just because I do > not think they describe things well enough. For instance, when I > first started using scp(1), I fought like hell before I figured it > out. I do not feel the manual page had a clear description of how > to use scp(1). It did, however, cover the options well... I think > that it should describe how to use protocol 2, I also think it should > point you to a reference of the use options. > > Opinions? My opinion is that this is absolutely clear to anybody who had ever read a manual page and knows that [] stand for optional things: SYNOPSIS scp [-pqrvBC46] [-F ssh_config] [-S program] [-P port] [-c cipher] [-i identity_file] [-o ssh_option] [[user@]host1:]file1 [...] [[user@]host2:]file2 It's absolutely clear that to copy from local to remote computer one uses: scp file1 user@host:file2 and from remote to local scp user@host:file1 file2 What's not clear about it? Careful reading of other ssh man pages makes it clear how to set up your public keys and config files. I don't have any complaints about ssh man pages and have a very positive experience with OpenSSH setup on my network compared with the comercial SSH about two or three years ago (confusion with adding 2 to everything [ssh2, sshd2], total inability to use old config files for anything, etc.) -- Zvezdan Petkovic http://www.cs.wm.edu/~zvezdan/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message