From ddc7a56ab00da36e511c7dba2f9e312360b8a7f8 Mon Sep 17 00:00:00 2001 From: Dirk Wetter Date: Fri, 17 Jan 2020 11:59:41 +0100 Subject: [PATCH] fix language --- etc/client-simulation.wiresharked.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/etc/client-simulation.wiresharked.md b/etc/client-simulation.wiresharked.md index edc8fd4..60c66d9 100644 --- a/etc/client-simulation.wiresharked.md +++ b/etc/client-simulation.wiresharked.md @@ -7,7 +7,7 @@ The whole process is done manually. * 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! Be also careful with Google Apps, especially on older devices as they might has an own TLS stack +* 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 come with an own/updated 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.