Date: Fri, 2 Dec 2011 17:22:57 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Adam Vande More <amvandemore@gmail.com> Cc: stable@freebsd.org Subject: Re: r228152: anyone got the None cipher working with base OpenSSH? Message-ID: <20111203012257.GA44866@icarus.home.lan> In-Reply-To: <CA%2BtpaK0a6C-F5GHef2J4OQ=tpvFcpKUC_syotY8FHVJOMm-RYg@mail.gmail.com> References: <CAOjFWZ4W1=TbLuMhi17shuYaNbGq18N1DWYLXiyiJ72gOM_6qA@mail.gmail.com> <20111202233220.GA43495@icarus.home.lan> <20111202233930.GA43590@icarus.home.lan> <CA%2BtpaK0a6C-F5GHef2J4OQ=tpvFcpKUC_syotY8FHVJOMm-RYg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 02, 2011 at 05:51:03PM -0600, Adam Vande More wrote: > On Fri, Dec 2, 2011 at 5:39 PM, Jeremy Chadwick <freebsd@jdc.parodius.com>wrote: > > > If the WARNING message that is output to stderr > > bothers you, use -T. > > > > This says -T disables the NONE cipher: > > http://www.psc.edu/networking/projects/hpn-ssh/none.php > > I haven't looked at current patches so maybe doesn't apply. No, you're correct -- use of -T disables the none cipher. I only checked actual packets (for plain-text) with tcpdump when testing the above **without** -T. I found that -T disabled the warning message; well duh, because it disables the none cipher. TL;DR -- my above message ("use -T to disable the warning") is absolutely wrong. The WARNING message to stderr, when a tty is allocated, cannot be disabled to my knowledge -- the -n flag should inhibit it, and I imagine this is intentional so that admins can use -oCipher=none for backups on LANs, etc.. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111203012257.GA44866>