Obfuscation Evaluation 2016

Task

We call an obfuscation software

• safe, if a forensic analysis does not reveal the original author of its obfuscated texts,
• sound, if its obufscated texts are textually entailed with their originals, and
• sensible, if its obfuscated texts are inconspicuous.

These dimensions are orthogonal; an obfuscation software may meet any of them to various degrees of perfection.

The task is to devise and implement performance measures that quantify any or parts of these aspects of an obfuscation software.

Input

We will provide you with the data generated by submitted obfuscation software as soon as it becomes available.

The input format will be the same as the output of the author masking task.

Output

The output of an evaluation software should be formatted as follows:

measure {
  key  : "myMeasure"
  value: "0.567"
}
measure {
  key  : "myOtherMeasure"
  value: "1.5789"
}
measure {
  key  : "myThirdMeasure"
  value: "0.98421"
}
...

The output is formatted as ProtoBuf text, not JSON.

• key can be any string that clearly and concisely names the performance measure.
• value shall be a numeric quantification of the measure for a given obfuscated text.

Task Committee