id summary reporter owner description type status priority milestone component version severity resolution keywords cc distribution status_field 3203 Need to check Sugar for places where we might break on invalid data from the outside sascha_silbe sascha_silbe "#3200 has shown that we need to be careful about any data we get passed from the outside, e.g. via activity bundles. Invalid data from the outside - regardless whether it's because of user (developer) mistake, corrupted files or even outright malice - should not be be able to impact regular Sugar operation. We need to audit all places where we handle data from the outside and check for potential breakage. Hardening e.g. sugar-toolkit against broken icons doesn't help: 1. If a system icon is broken, we'll want to know that. 1. Different parts of the system will want to take different actions (e.g. different default icons) for invalid data. " task closed Unspecified by Maintainer Sugar Git as of bugdate Major wontfix New