On 05/04/15 15:37, Murray S. Kucherawy wrote:
> However, if that's really what everyone wants, I'm willing to have a
> command line flag that defaults to the current "harsh" behavior, but can
> be set to do the warning thing. We need to document the obvious dangers
> of enabling it, and come to some agreement on how long the grace period
> should be.
>
> So far though, we don't have consensus either way. I've seen two people
> in favor (Andreas and SM) and two opposed (Steve and myself). What do
> others think?
I am of the belief that security-related changes, particularly ones that
disable or drop support for security-related features, should ALWAYS be
flagged IMMEDIATELY. You never know who or what might be relying on
that feature being there.
--
Phil Stracchino
Babylon Communications
phils_at_caerllewys.net
phil_at_co.ordinate.org
Landline: 603.293.8485
Received on Mon May 04 2015 - 20:16:21 PST