2
edits
Phishing Protection: Server Spec: Difference between revisions
Jump to navigation
Jump to search
Phishing Protection: Server Spec (view source)
Revision as of 00:15, 3 February 2007
, 3 February 2007→Message Authentication Code for Table Updates
| Line 182: | Line 182: | ||
=== Message Authentication Code for Table Updates === | === Message Authentication Code for Table Updates === | ||
The client provides a wrapped key to the server which the server needs to convert into the shard client key; see above. The MAC is computed from an MD5 Digest over the following information: client_key|separator|table data|separator|client_key. The separator is the string :coolgoog: - that is a colon followed by "coolgoog" followed by a colon. The resulting 128-bit MD5 digest is websafe | The client provides a wrapped key to the server which the server needs to convert into the shard client key; see above. The MAC is computed from an MD5 Digest over the following information: client_key|separator|table data|separator|client_key. The separator is the string :coolgoog: - that is a colon followed by "coolgoog" followed by a colon. The resulting 128-bit MD5 digest is websafe base-64 encoded and provided via [mac=<encoded digest>] on the first line of a table update; see above. | ||
Here is an example, that you can use to verify the MAC algorithm in your server: | Here is an example, that you can use to verify the MAC algorithm in your server: | ||