Wireshark-users: Re: [Wireshark-users] dissecting HTTPS traffic
From: Hugo van der Kooij <[email protected]>
Date: Tue, 13 Oct 2015 08:06:19 +0000

Most firewalls and proxies that do something with URLs and/or content have SSL intercept capabilities.



Van: [email protected] [mailto:[email protected]] Namens Noam Birnbaum
Verzonden: dinsdag 13 oktober 2015 01:33
Aan: Community support list for Wireshark <[email protected]>
Onderwerp: Re: [Wireshark-users] dissecting HTTPS traffic


Curious, why wouldn't you recommend doing our own MITM attack? (And how would we do it?)


On Mon, Oct 12, 2015 at 11:22 AM, Mark Semkiw <[email protected]> wrote:

All you can really do at that point is analyze the endpoints and see if you can get any info from that.  Well I guess you could setup your own man-in-the-middle attack, but I wouldn’t suggest it.


Mark Semkiw, Senior Network Engineer





Met vriendelijke groet / With kind regards,

Hugo van der Kooij
network engineer

Delft - Noord-Oost - Zuid

T: +31 15 888 0 345  F: +31 15 888 0 445
E: [email protected]  I:  www.qi.nl

From: <[email protected]> on behalf of Noam Birnbaum
Reply-To: Community support list for Wireshark
Date: Friday, October 9, 2015 at 4:12 PM
To: "[email protected]"
Subject: [Wireshark-users] dissecting HTTPS traffic


Hey folks,


One of our clients has recently been having their WAN bandwidth eaten up, and we've narrowed it down to one executive's computer.


Now we want to dissect that computer's traffic to see what it's doing. However, much of it is HTTPS, so we can't see the content. Any suggestions on getting a useful analysis?



Sent via:    Wireshark-users mailing list <[email protected]>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:[email protected]?subject=unsubscribe