Date: Fri, 17 Oct 2014 22:43:39 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Ben Woods <woodsb02@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: ssh None cipher Message-ID: <alpine.GSO.1.10.1410172242240.27826@multics.mit.edu> In-Reply-To: <CAOc73CCvQqwg65tt9vs54CoU1HGvV7ZxLWeQwXiSOm8UjtV50w@mail.gmail.com> References: <CAOc73CCvQqwg65tt9vs54CoU1HGvV7ZxLWeQwXiSOm8UjtV50w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 Oct 2014, Ben Woods wrote: > Whilst trying to replicate data from my FreeNAS to my FreeBSD home theater > PC on my local LAN, I came across this bug preventing use of the None > cipher: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163127 > > I think I could enable the None cipher by recompiling base with a flag in > /etc/src.conf. I agree. > Is there any harm in enabling this by default, but having the None cipher > remain disabled in /etc/ssh/sshd_config? That way people wouldn't have it > on my default, but wouldn't have to recompile to enable it. I do not see any immediate and concrete harm that doing so would cause, yet that is insufficient for me to think that doing so would be a good idea. -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1410172242240.27826>