1
edit
Phishing Protection: Server Spec: Difference between revisions
Jump to navigation
Jump to search
m
Phishing Protection: Server Spec (view source)
Revision as of 15:52, 21 February 2007
, 21 February 2007→Encrypted Hash Format
| Line 214: | Line 214: | ||
** 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. | ||
** The first 8 characters of the decoded data are being used as random salt for the encryption key. The encryption/decryption key is constructed by computing the MD5 hash over ' | ** The first 8 characters of the decoded data are being used as random salt for the encryption key. The encryption/decryption key is constructed by computing the MD5 hash over 'database salt|random salt|hostname'. This results in a 128-bit key. | ||
** Use RC4 to decrypt the remaining data with the decryption key from above. | ** Use RC4 to decrypt the remaining data with the decryption key from above. | ||
** Split on '\t' (tab stop) to create an array of regular expressions. | ** Split on '\t' (tab stop) to create an array of regular expressions. | ||