27
edits
Phishing Protection: Server Spec: Difference between revisions
Jump to navigation
Jump to search
→Encrypted Hash Format
| Line 211: | Line 211: | ||
* Split the canonical hostname into an array of hostname components by splitting on the 'dot', e.g. "www.sub.acme.com" gets turned into the array [www sub acme com] | * Split the canonical hostname into an array of hostname components by splitting on the 'dot', e.g. "www.sub.acme.com" gets turned into the array [www sub acme com] | ||
* For each sub-hostname, e.g. "www.sub.acme.com", "sub.acme.com", "acme.com", do the following: | * For each sub-hostname, e.g. "www.sub.acme.com", "sub.acme.com", "acme.com", do the following: | ||
** Compute the MD5 hash of the database salt concatenated with the sub-hostname string and uppercase the result, for example, "www.sub.acme.com" results in "F64932D7EE9CEAEBA3DED3689C5A77CA" and "sub.acme.com" results in "819C6791744F94B7C425FA81B09B0751 | ** Compute the MD5 hash of the database salt concatenated with the sub-hostname string and uppercase the result, for example, "www.sub.acme.com" results in "F64932D7EE9CEAEBA3DED3689C5A77CA" and "sub.acme.com" results in "819C6791744F94B7C425FA81B09B0751". | ||
** If the resulting key cannot be found in the table, continue with the next sub-hostname, otherwise continue with the data below. | ** If the resulting key cannot be found in the table, continue with the next sub-hostname, otherwise continue with the data below. | ||
** Decode the data by unencoding the regular base64 encoding. | ** Decode the data by unencoding the regular base64 encoding. | ||