I
ID
Hi,
When a new application is going to be executed, WM does the code
signing verification and ask the user to run or not the application
(i.e. "The program if from an unknown publisher. Running it can
possibly harm your device. Do you want to continue?"). If the user
accepts to run the application, WM is not going to ask again if the
user want to run the application. However, if the application is
modified (i.e. changing a bit of the binary file), WM ask you again the
same question, as the application were new.
My conclusion is that WM keeps a database with the integrity hash of
each application the user have accepted to run, maybe in the system
registry.
Can somebody explain me how this verification works in WM5 or where to
find information about it?
Thanks,
ID
When a new application is going to be executed, WM does the code
signing verification and ask the user to run or not the application
(i.e. "The program if from an unknown publisher. Running it can
possibly harm your device. Do you want to continue?"). If the user
accepts to run the application, WM is not going to ask again if the
user want to run the application. However, if the application is
modified (i.e. changing a bit of the binary file), WM ask you again the
same question, as the application were new.
My conclusion is that WM keeps a database with the integrity hash of
each application the user have accepted to run, maybe in the system
registry.
Can somebody explain me how this verification works in WM5 or where to
find information about it?
Thanks,
ID