You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the user-mode tool can choose the location of the image file. We
need some mechanism to avoid this - there should be a fixed location, so that
attackers can't overwrite arbitrary files.
Original issue reported on code.google.com by sebastian.poeplau on 29 Jun 2012 at 9:08
The text was updated successfully, but these errors were encountered:
Implemented a twofold solution: At compile time, the user can choose whether
the image file name is stored in the registry or hard-compiled into the code.
The former allows to change the image location with certain privileges while
the latter makes it completely static.
Original comment by sebastian.poeplau on 2 Aug 2012 at 12:48
Original issue reported on code.google.com by
sebastian.poeplau
on 29 Jun 2012 at 9:08The text was updated successfully, but these errors were encountered: