Bug#780797: Package modifying a user-modified config file? [Bug #780797]
On Sun, Mar 22, 2015 at 11:18:03PM +0100, Christoph Anton Mitterer wrote:
> On Sun, 2015-03-22 at 20:35 +0000, Colin Watson wrote:
> > Due to what I view as historical errors, sshd_config doesn't really have
> > a single canonical state on all upgraded systems. If it had been a
> > dpkg-managed conffile from the start then that would have been much
> > better, but as it is we have to make do with what we have.
> Well maybe it's time to make a clear cut:
> - declare all previous configs no longer "handled" by future upgrades in
> stretch
> - create fresh default config, which also got rid of all other
> questionable Debian modifications
> - make it dpkg managed
>
> That could also greatly simplify the maintainer scripts.
I'm afraid I'm not interested in the very considerable amount of work
required to get there well.
> Well if people don't read their NEWS.Debian files and their release
> notes it's simply their fault.
> You cannot just protect them from everything, and you make your own life
> as maintainer much harder... and others who do their admin homework
> kinda suffer as well.
You are entitled to your opinion, but I respectfully disagree.
> But to be honest, and without intending to offend any of the others,...
> it kinda seems to me that people make a mountain out of a molehill.
>
> The change is really little, for well grounded security reasons it's
> actually intended by upstream that non env vars are send/accepted unless
> explicitly allowed by the admin. So people who complain now likely just
> abused that "hole" in Debian's default all the years, which is however
> no grant for a right to do so forever.
I disagree with you that this is a problem worth fixing. If you
consider this a "hole", well, I'll just have to live with that.
--
Colin Watson [cjwatson@debian.org]
Reply to: