![]() This means you can iterate through the site list until you find a MD5 hash of AccountKe圜ode that matches the HPL key in the registry to systematically determine the correct site by only using information available to the endpoint. In the site information obtained from the API, AccountKe圜ode stores the site key (without dashes). The use of the HPL registry key and MD5 hash of the site key makes it possible to directly determine the site id for a particular endpoint without knowing it. Since querying endpoint information via the API requires the Site ID as well, it was not possible previously to systematically determine the site ID required without using and providing a site name match. So while you can’t determine the site key from the MD5 hash, you can verify the MD5 hash if you have the site key. The HPL registry key is a MD5 hash of the site key (without dashes). I discovered that this isn’t entirely true. The only information available is the HPL Key value in the registry at “HKLM:\SOFTWARE\Wow6432Node\WRData\HPL” and this is an encrypted value for the key, so it isn’t possible to determine the key in use, although it would be the same value for all endpoints in a site. It may greatly help those developing their own API scripts.įor some time support has said that there is no way to determine the key in use on a particular system systematically. I made a relatively big discovery today, and would like to share. Webroot® Legacy Products (2011 and Prior) 33. ![]() Webroot® SecureAnywhere™ - Antivirus for PC Gamers 553.Webroot® Security Awareness Training 53.Webroot® Business Endpoint Protection 1130.Webroot Mobile Security for Android 936.Webroot® Consumer/Business - for Macs 368.Webroot® SecureAnywhere™ - Complete 3821.Webroot® SecureAnywhere™ - Internet Security Plus 2467.Webroot® SecureAnywhere™ - Antivirus 6968.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |