Bug 36340

 Tom Rhodes wrote:
 > 
 > I reread this pr, and feel strongly that it can be closed.
 > Any objections?  I have been personally lurking the FreeBSD-security
 > mailing list for about 2-3 weeks, and the only thing I have read about
 > are security questions in general, mainly things like if I get this
 > error.  I feel that the security mailing list is fine how it is, as
 > the stated problems do not seem to be occuring right now...
 > 
 
 Well, I object.  The list charter clearly states, "This is a 
 technical mailing list for which strictly technical content 
 is expected."  So in addition to the original PR, it would be 
 appropriate to move -security from the general lists section 
 to the technical lists section.  I know the word "technical" 
 gets thrown around a lot without definition, but a little 
 consistency would be nice.
 
 The threads in -security on Saturday (digest #464) were: a long 
 rambling speculative discussion about how to provide remote root 
 login without a password (I don't know what the original question 
 was); someone who needed help reading the su(1) man page; a 
 question about how to configure maildrop and whether maildrop or 
 procmail has better security; the usual FAQ about "microuptime 
 went backwards"; and a question about file permissions in /tmp. 
 Of these, only the last is both FreeBSD-specific and security-specific 
 and thus clearly within the list charter (although it was probably 
 resolved by reading a man page somewhere and is probably a FAQ).  
 All of the rest either clearly belong on -questions or are 
 arguably more appropriate there.  
 
 In other words, the stated problem IS occuring now.
 
 All of that is, in my opinion, only marginally relevant.  The 
 issue at hand is that the Handbook description of -security does 
 not accurately summarize the list charter (however vague it may 
 be), and should be refined to do so.  Perhaps "Technical discussion 
 of FreeBSD-specific security issues" would do it.
 
 I'll be happy to post the issue on the -security list and 
 see what people think, but I believe it is clear that either 
 the list charter or the Handbook description needs to be changed 
 so they are consistent with each other.
 
 And it may be that there should be another list: -security-questions, 
 which would absorb most of the questions now posted on -security, 
 and allow it to return to technical discussions of FreeBSD-specific 
 security issues, and what to do about them.
 
 
 > Opions?
 
 Now you have mine.  I'll post the issue on -security and see if 
 there is a clear consensus.  I'll probably regret it, since it 
 doesn't fall within the list charter 8)
 
 
 - Bob
 
 > 
 > --
 > Tom (Darklogik) Rhodes
 > www.Pittgoth.com Gothic Liberation Front
 > www.FreeBSD.org  The Power To Serve