RFR : 8225345: Provide Cloud IAAS related info on Linux in the hs_err file

[John Rose]

On Jun 7, 2019, at 9:18 AM, Kodewerk <kirk at kodewerk.com> wrote:
> 
> I have to agree with you. As it stands, the hs_err does not contain any information that cannot be passed to me with the need of an NDA. Once you start digging deeper into the end users environment you start raising serious security concerns. I would suggest that this information should be collectable in anger and not by default.

+1 from me on this thread also.  I like the suggestion of a
public wiki doc that says what's in and what's excluded from hs_err.

One more idea about adding more information "in anger":
This added information could be packaged separately, in a different
file from hs_err.  Occasionally mixing secrets into usually non-secret
channels is an anti-pattern.  If there's value in keeping hs_err
non-confidential, occasional opt-in confidential info should go into
a separate bucket.  The usability problem of having to manage
two buckets instead of one is not enough to outweigh the value
of keeping stuff properly labeled.