> https://cwiki.apache.org/confluence/display/TS/Debug+Tag+Guideline
This is interesting. This would provide what is basically an access label at the granularity of a log statement, which is a way to enforce a mandatory access control where certain logged data may be sensitive. One could see this taken even further such that individual log fields could be given differing labels and a high water mark used to determine to which destination/"facility" the statement is logged. Looking at the draft, there would be some design work still needed before a formal proposal could be made. But I think it is a very interesting direction to take for log data that others have done with big data generally. I was planning to make a small enhancement to s3_auth when I noticed this. And I think what I'd like to do here is remove just the sensitive field from the log statement for now. [ Full content available at: https://github.com/apache/trafficserver/pull/4260 ] This message was relayed via gitbox.apache.org for [email protected]
