Matthew Newton via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
There's no need to try and look out for the right bit of debug output to send. People nearly always send what they think is useful, which often isn't (or not complete enough), and then we get annoyed about not having the right information to be able to help. This happens a lot, hence the rapid descent into frustration.
I think there are two factors that keep people from doing so, and both share the same root cause: the debug information is usually an immense really ugly looking thing that A) they would not normally post on a discussion/chat for fear of being "messy", and most people these days grew up with discussions/chats so they view a mailing list through that lens and B) Is full of details about what is most often a component of security infrastructure, where there is a concern about exposure requiring them to consider how to redact some details, some of which may not be amenable to a simple search/replace. Some sort of interactive post-processor for the debug input to pretty it up, clean out the true cruft, perform redactions/aliasing on any exposed server names or addresses, and maybe point out a few common issues if it sees them... might be a worthwhile endeavor.