{"id":204,"date":"2021-06-14T20:37:40","date_gmt":"2021-06-14T18:37:40","guid":{"rendered":"https:\/\/project.inria.fr\/espdms\/?page_id=204"},"modified":"2022-04-01T11:07:39","modified_gmt":"2022-04-01T09:07:39","slug":"game3","status":"publish","type":"page","link":"https:\/\/project.inria.fr\/espdms\/game3\/","title":{"rendered":"Game 3 – Malicious Employer"},"content":{"rendered":"\n
In this game, the employer’s App leverages its execution privilege to try to leak Points Of Interest of the user. Two versions of a malicious Data Task are available and they leak data differently.\nThe goal here is to run both versions and explain the malicious data tasks logic and their differences. In particular, what is the precise leaking strategy that each Data Task implement ? If you want to submit your explanation, please use the form at the bottom of the page.\n<\/div>\n
\n\n\n\n
\n

PDMS version <\/strong><\/h2>\n
    \n
  • The Core enforces stateless data tasks: NO <\/span><\/strong><\/li>\n
  • The Core enforces deterministic data tasks: NO<\/span><\/strong><\/li>\n
  • The result size is limited to: 6 bits<\/span><\/strong><\/li>\n\n<\/ul>\n
    \n

    Note that: <\/h2>\n
      \n
    • A POI is encoded on two 24 bits numbers<\/li>\n
    • POIs are highly sensitives since they can reveal the PDMS owner habits, religion or sexual preferences.<\/li>\n<\/ul>\n
      \n
      \n<\/td>\n

 \"\"<\/td>\n \"\"<\/td>\n<\/tr>\n<\/td>\n