From ac7a20f018b092e18159278fb5db57059a46c7d7 Mon Sep 17 00:00:00 2001 From: Dirk Wetter Date: Thu, 16 Jan 2020 22:46:43 +0100 Subject: [PATCH] Update client-simulation.wiresharked.md --- etc/client-simulation.wiresharked.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/etc/client-simulation.wiresharked.md b/etc/client-simulation.wiresharked.md index 77458e0..edc8fd4 100644 --- a/etc/client-simulation.wiresharked.md +++ b/etc/client-simulation.wiresharked.md @@ -1,13 +1,13 @@ This file contains client handshake data manually created from Wireshark. The content needs to be added to client-simulation.txt which other part -comes from the SSLlabs client API via update_client_sim_data.pl +comes from the SSLlabs client API via ``update_client_sim_data.pl`` The whole process is done manually. ## Instructions how to add a client simulation: * Start wireshark at a client or router. Best is during capture to filter for the target of your choice. * Make sure you create a bit of encrypted traffic to your target. Attention, privacy: if you want to contribute, be aware that the ClientHello contains the target hostname (SNI). -* Make sure the client traffic is specific: For just "Android" do not use a browser! Use the play store app e.g.. +* Make sure the client traffic is specific: For just "Android" do not use a browser! Be also careful with Google Apps, especially on older devices as they might has an own TLS stack * Stop recording. * If needed sort for ClientHello. * Look for the ClientHello which matches the source IP + destination you had in mind. Check the destination hostname in the SNI extension so that you can be sure, it's the right traffic.