Date: Wed, 27 Mar 2002 11:30:22 -0500 From: Tom Rhodes <darklogik@pittgoth.com> To: Michael Lucas <mwlucas@blackhelicopters.org> Cc: dan@tangledhelix.com, freebsd-security@FreeBSD.ORG Subject: Re: It's time for those 2048-, 3072-, and 4096-bit keys? Message-ID: <20020327113022.00351ae5.darklogik@pittgoth.com> In-Reply-To: <20020327105531.A88300@blackhelicopters.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> <20020327105531.A88300@blackhelicopters.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=.V_r(hBot7Uk+ox Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 27 Mar 2002 10:55:31 -0500 Michael Lucas <mwlucas@blackhelicopters.org> wrote: > On Wed, Mar 27, 2002 at 11:01:00AM -0500, Tom Rhodes wrote: > > On Wed, 27 Mar 2002 07:42:36 -0500 > > Michael Lucas <mwlucas@blackhelicopters.org> wrote: > > > > > > Perhaps a comment in the file, "we recommend using v2 whenever > > > possible", so people stumble across it frequently even if they > > > don't bother reading the docs? > > > > 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. > > Certainly a possibility. However, this is contrib code. Be sure to > ask your mentor about altering contrib code. Upon investigation, I > see that even the config file is contrib code. > > Heck, Tom, you're a FreeBSD committer now, certainly you could > become an OpenSSH -doc committer too. :-) Haha ;) I'll be honest, my mailbox is full already. I'll come up with some kind of an idea. At first, the ideas that came to me were to edit the committers guide and/or email the OpenBSD project, in that aspect, maybe I can kill 2 birds with one stone. Is there a reason that the ssh(1) information in the committers guide a little, well, out of date? > > ==ml > > -- > Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org > my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons > > http://www.blackhelicopters.org/~mwlucas/ > -- Tom (Darklogik) Rhodes www.FreeBSD.org -The Power To Serve www.Pittgoth.com -Pittgoth Discussion Portal trhodes@ {Pittgoth.com, FreeBSD.org} --=.V_r(hBot7Uk+ox Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) iD8DBQE8ofOiwPmgiRuevUMRAk5bAJ42lIMr1l6Zr+NSZDDt3wOHhewrfwCgqsLg twWTOKsi1w6w/+LrOUd7f5Y= =0VWr -----END PGP SIGNATURE----- --=.V_r(hBot7Uk+ox-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020327113022.00351ae5.darklogik>