Mikhail T. <mi+thun <at> aldan.algebra.com> writes: > > On 23.12.2012 11:48, Chris Rees wrote: > > They involve a lot of thought to get right, as well as chmod g-w on > > something where you probably meant chmod go-w is a disastrous but > > (perhaps) common error. Chris > > Well, in (over 20) years of dealing with Unix, I've never made a mistake > like that, nor do I understand, how it can be considered "common" ... > Got to admit, I was surprised to see it. It made me think, I do not > understand something -- or that FreeBSD is becoming overly > paternalistic. It turned out to be the latter... > > I doubt, it is useful. Worse, issuing such warnings routinely, only > reinforces the unfortunate misconceptions like the one Barney > demonstrated in this thread. When originally added, the check was meant > to be off by default: > ... > perhaps, it should have remained off? Yours,
Those security checks are for a reason - people make mistakes (even a perfect guy like you will have a "head in a brown bag" time). It is better to get a heads-up, then think about it and turn it off (customize) if considered unneeded. jb _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
