Comment 3 for bug 54180

Philip Hands <email address hidden> writes:

> The description from /usr/doc/ssh/README.CIPHERS makes it fairly
> clear that this is a bad idea, and since blowfish runs at about 88%
> of none's speed, you will normally not notice the difference.

OK, I hadn't read that. And assuming that idea is the default, I can
probably switch to blowfish and be reasonably happy.

> Of course, if you want to do this for yourself, you just need to
> specify --with-none to configure. Feel free to persuade me
> otherwise.

I feel this falls in the "user choice" arena. As long as "none" is
not the default, and you have to do something to explicitly ask for
it, it's fine. Preventing the user from using "-c none", to me, would
be similar to removing the --force options from dpkg, or the -f option
from e2fsck. I admit that these aren't perfect analogies, but they at
least convey the domain under which I feel this issue falls.

Thanks

--
Rob Browning <email address hidden>
PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30