Re: [cross-project-issues-dev] Error reporter and third-party code
IMHO, the 20% who explicitly enabled message anonymization will also
enable method anonymization because they are avoiding the problem of
needing corporate approval of any release of data. A method name such as
SHA4096 may reveal what algorithm is being exploited/developed. Too
risky if you are not sure.
> My proposal: When a we detect a non-OSS stack frame,
> we actively ask the user to make a choice that’s then persisted for
that instance of Eclipse.
'instance of Eclipse' is ambiguous.
If the choice is persisted in the workspace that seems too dangerous,
one accidental answer and Eclipse becomes leaky.
Persisting only until the next Eclipse restart seems like a good idea.
On 22/07/2015 22:39, Marcel Bruch wrote:
Sounds okay to me. I wonder if the short cut „not to enable 3rd party class names in stack traces by default“ would be acceptable as well since it’s right on the configure dialog and easy to grasp (IMHO).
any thoughts on this? I can change the defaults (for SR1) if the EF would agree.
FWIW, during the milestone build (until June 20th) 20% of the users explicitly enabled „message anonymization“ because they feared that the message may contains sensitive data. I’d expect that users are less concerned about method names. I’d need to validate this number with the current reporter base to give a more reliable statement, though.
I brought up the issue of better handling third-party plugins several times from the very beginning and was brushed off.
I strongly conclude that if someone would have cared at that time, they would have had the chance to participate from the very first moment.
I did a quick search for earlier discussions on this topic and found  from August 2014. I don’t have the impression you were brushed off in that discussion - but nevertheless: If I did (there or somewhere else) I apologize for that.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6081 / Virus Database: 4392/10286 - Release Date: 07/22/15