Abstract:
A method and user device for preventing unauthorized viewing of at least one entity, e.g. character, digit, image and/or shape, is provided. The method comprises splitting up the entity in at least two parts, after which one of the split parts are sent to a first display unit and the remaining split part(s) is/are sent to at least one other display unit.
Abstract:
A method, executed by a data processing device, for verifying authenticity of a client program executed on a processing device, the method comprising: receiving one or more messages from the processing device, and verifying authenticity of the client program based on one or more properties of the received messages; repeatedly updating a first part of the client program, wherein different instances of the first part of the client program cause messages sent by the processing device to have respective detectable properties indicative of the instance of the first part of the client program.
Abstract:
A technique for determining a malign or non-malign behavior of an executable file is disclosed. In a first method aspect, the method comprises the steps of first acquiring a first behavior profile of the executable file, the first behavior profile comprising a first observable execution trace of the executable file from an emulated environment, second acquiring a second behavior profile of the executable file, the second behavior profile comprising a second observable execution trace of the executable file from a real environment, and comparing the first and second observable execution traces so as to determine the malign or non-malign behavior of the executable file. In another method aspect, the method comprises the steps of receiving a trigger condition, collecting, responsive to the trigger condition, first and second behavior profiles of the executable file from first and second one of two or more file-execution devices, the first and second behavior profiles comprising first and second observable execution traces of the executable file, and the first and second observable execution traces being non-mapped to the first and second file- execution device, respectively.