| OLD | NEW |
| (Empty) | |
| 1 h |
| 2 ================== |
| 3 One time setup |
| 4 =================== |
| 5 |
| 6 --------------------------- |
| 7 1. Apply this patch |
| 8 --------------------------- |
| 9 |
| 10 $ git new-branch CERT_MAPPER |
| 11 $ git cl patch 1238413004 |
| 12 |
| 13 --------------------------- |
| 14 2. Download CT database |
| 15 --------------------------- |
| 16 |
| 17 If you haven't already, you need to download the full CT database. This takes a |
| 18 long time (order of hours), and will save a file about 22GB large. (If you know |
| 19 someone that has already downloaded this, you may want to copy it from them |
| 20 instead of fetching it yourself.) |
| 21 |
| 22 $ cd src |
| 23 $ ./net/tools/ct_mapper/sync-ct-database.sh CT.db |
| 24 |
| 25 --------------------------- |
| 26 3. Dump all the certificates from CT database |
| 27 --------------------------- |
| 28 |
| 29 Rather than operate directly on the CT database, the cert mapper iterates over |
| 30 a simpler (and smaller) file, which just contains the DER for each certificate. |
| 31 This file is about half the size of the CT.db (making it around 11GB). |
| 32 |
| 33 $ cd src |
| 34 $ ./net/tools/ct_mapper/dump-ct.sh CT.db CERTS_DUMP_PATH |
| 35 |
| 36 This will take about 20 minutes to run, after which CERTS.bin will have been |
| 37 written. This is the input file that you pass to the cert_mapper. |
| 38 |
| 39 ====================================================== |
| 40 How to run code over the certificates in CT database (or a PEM file) |
| 41 ====================================================== |
| 42 |
| 43 Add your code into: |
| 44 net/tools/ct_mapper/my_visitor.cc |
| 45 |
| 46 And then execute: |
| 47 |
| 48 $ cd src |
| 49 $ ninja -C out/Release cert_mapper |
| 50 $ ./out/Release/cert_mapper CERTS_DUMP_PATH |
| 51 |
| 52 NOTE: If you get "ninja: error: unknown target 'cert_mapper'" then you need to |
| 53 re-generate the ninja files with "gn gen out/Release" |
| OLD | NEW |