Thank you Matthew for your perspective.
Regarding your two conditions:
1) Broader discussion
I agree this is needed. I note that some of the committee's deliberation
happened privately, which may have limited the range of perspectives
considered so far. Would it be possible to move the remaining discussion
to a public venue to gather wider input?
2) Explicit maintainer statement
In the original bug #1124968, Michael wrote:
> I wont argue any more here, there's no point.
> If you feel the default [...] should be changed, please ask the
security team or a technical committee.
This read as a clear refusal to act. However, Michael's subsequent
message in this thread (#17) concluded that "unbound should not enable
the resolvconf hook by default," aligning with my position. His current
stance is therefore unclear, and I think hearing from him directly would
help everyone.
Michael, could you clarify your current position?
One additional point
I'd like to raise a question I haven't seen addressed: what was the
original justification for enabling this hook by default? The script
itself notes it was disabled for several releases before being
re-enabled. If there was no broad user demand for this change, while
introducing the privacy and security concerns discussed here, that would
be a strong argument for reverting to the previous default.
I hear Matthew's point about collaboration, and I appreciate the
committee's time on this. I'll keep my contributions constructive going
forward.
LRob
