Re: dissecting HTTPS traffic

[Hugo van der Kooij <hugo.van.der.kooij () qi nl>]

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


Van: wireshark-users-bounces () wireshark org [mailto:wireshark-users-bounces () wireshark org] Namens Noam Birnbaum
Verzonden: dinsdag 13 oktober 2015 01:33
Aan: Community support list for Wireshark <wireshark-users () wireshark org>
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 <Mark.Semkiw () commtrans org<mailto:Mark.Semkiw () commtrans org>> 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

CCNA  CNSE  WCNA




Met vriendelijke groet / With kind regards,



Hugo van der Kooij
network engineer

[cid:image8e137e.JPG@99326095.478c2249]<https://www.qi.nl/over-qi-ict>

Delft<https://www.qi.nl/vestigingen#delft> - Noord-Oost<https://www.qi.nl/vestigingen#Qi-ict-noordoost> - 
Zuid<https://www.qi.nl/vestigingen#qi-ict-zuid>
[cid:imagea90636.PNG@c0e12137.4bb76758]<http://www.facebook.com/qiict>  [cid:image0f9ba5.JPG@6b007175.4c9cb92e] 
<https://nl.linkedin.com/company/qi-ict>        [cid:image8fae21.JPG@cea20349.41a07f54] <http://twitter.com/qiict>      
[cid:image57836e.JPG@37d236b4.4c8abffb] <http://www.youtube.com/user/QiictDelft>


T: +31 15 888 0 345     F: +31 15 888 0 445
E: hugo.van.der.kooij () qi nl<mailto:hugo.van.der.kooij () qi nl>    I:  www.qi.nl<http://www.qi.nl>





From: <wireshark-users-bounces () wireshark org<mailto:wireshark-users-bounces () wireshark org>> on behalf of Noam 
Birnbaum
Reply-To: Community support list for Wireshark
Date: Friday, October 9, 2015 at 4:12 PM
To: "wireshark-users () wireshark org<mailto:wireshark-users () wireshark org>"
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?

Thanks!

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org<mailto:wireshark-users () wireshark org>>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org<mailto:wireshark-users-request () wireshark 
org>?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe