Reproducibility instructions for CCR paper on TLS 1.3 evolution
We apologise for the need to distribute data sets and tools across several locations and repositories. Data is generally too large to store centrally, but we will endeavor to honor any reviewer request for transfer of larger chunks of data. Tools are often developed inside their own repositories; we link to these.
Ralph Holz, Jens Hiller, Johanna Amann, Abbas Razaghpanah, Thomas Jost, Narseo Vallina-Rodriguez, and Oliver Hohlfeld. SIGCOMM Comput. Commun. Rev., 50(3). DOI: https://doi.org/10.1145/3411740.3411742
Data sets and measurement tools
We provide IP ranges as determined by us for the chosen providers in
preparation/mappings, you find key-value pairs of scan timestamps to respective months. Some of our analysis scripts use these to automatically figure out which file to load next. The scripts have environment variables that you can point at the directory holding the mappings.
Active scans (TLS 1.3 drafts)
Our usage of our modified zgrab scanner for the scanning of TLS 1.3 draft support is detailed in
active-scans-drafts. This directory provides helper scripts to build the scanner as well as usage examples. The scripts already set up the source code which is available here: zgrab, zcrypto
Active scans (RFC)
Our RFC-based scanner is published in this repository. We provide the scripts to run the scans in the directory
active-scans/run-scans/ in this repo.
Our data sets are massive. We are currently offering the output data for all our scans, but the PCAPs for just 2019-05 because they need 0.5TB storage alone. We are happy to offer all PCAPs via direct transfer if requested.
For our passive TLS 1.3 measurements, we cannot release the data for privacy reasons. We can provide high-level statistics in the paper. For reproducibility, we publish the entirety of our passive measurement pipeline in this repository.
Android and Lumen
Active scans (RFC)
Android data analysis
The script used to analyze the Lumen dataset can be found on this repository.