Confirmed users
908
edits
Services/Shavar: Difference between revisions
Jump to navigation
Jump to search
→List types: use the "format" terminology and update the dead link to the spec
(→Names: update this section to match recent usage and also the parts that are hard-coded in the client) |
(→List types: use the "format" terminology and update the dead link to the spec) |
||
| Line 22: | Line 22: | ||
: one of two formats at the time of writing: '''shavar''' and '''sha256'''. More on the formats below. | : one of two formats at the time of writing: '''shavar''' and '''sha256'''. More on the formats below. | ||
===== List | ===== List formats ===== | ||
The two different | The two different formats of lists currently supported are named '''shavar''' and '''sha256'''. While both publish hashes of the actual data sets they do so in slightly different ways. shavar lists use the hash prefix style of publication described in the [https://developers.google.com/safe-browsing/v3/update-guide Safe Browsing] protocol specification while sha256 lists publish the entire hash (all 32 bytes) rather than just the first 4 bytes of a hash. As a result, any list published in a shavar format has to "phone home" to the service to fetch an entire hash. | ||
==== How to Publish a new data set via the Safe Browsing protocol at Mozilla ==== | ==== How to Publish a new data set via the Safe Browsing protocol at Mozilla ==== | ||