SHARE
Preserving privacy in executable code.
We use the “secure triggers” technique of [FKSW03] for preserving privacy for code run on untrusted environments. To be more precise, using this technique a developer can mark certain information within a program that he wants to keep secret, he can establish certain “declassification” conditions, and produce a protected build of the program such that the information is mantained encrypted until the specified conditions are reached.