Sorry, here's the forgotten Gist:
https://gist.github.com/dlenski/33bfa3a8691686d02ddaf7a51843a89a
On Tue, Sep 4, 2018 at 2:42 AM, Brandon Liles wrote:
> Client Version:
>
> Pulse Secure 5.3.4 (1183)
>
> I did install the root Fiddler MITM cert and Fiddler automatically
> creates certs on the
Client Version:
Pulse Secure 5.3.4 (1183)
I did install the root Fiddler MITM cert and Fiddler automatically
creates certs on the fly for the sites you visit for HTTPS decryption
if you've enabled that feature.
Right now I get stuck just after the following two requests to the
Pulse endpoint,
On Mon, Sep 3, 2018 at 3:39 AM, Brandon Liles wrote:
> I haven't had any success trying to MITM the Pulse Secure handshake.
> With Fiddler on Windows, after setting up HTTPS decryption, the client
> just spins saying "Connecting".
Which version of the Pulse/NC client are you testing with?
Did
On Mon, Sep 3, 2018 at 3:27 AM, Andy Tsvetinskiy
wrote:
>
> I could compile debug versions of openconnect and test with verbose logging.
> Please let me know. Try to help
You don't need to compile any special version of openconnect. Running
`openconnect - --dump` should get you all the
On Mon, Sep 3, 2018 at 2:00 AM, Andreas Gnau wrote:
>
> Hello Daniel,
> I am experiencing the same problem. Thanks for bringing this up to a wider
> audience and doing the research. I have done the same kind of research a few
> months ago and I came to the same conclusion that many encountered
I haven't had any success trying to MITM the Pulse Secure handshake.
With Fiddler on Windows, after setting up HTTPS decryption, the client
just spins saying "Connecting".
On Mon, 2018-09-03 at 11:00 +0200, Andreas Gnau wrote:
> Hello Daniel,
> I am experiencing the same problem. Thanks for
Hello Daniel,
I am experiencing the same problem. Thanks for bringing this up to a
wider audience and doing the research. I have done the same kind of
research a few months ago and I came to the same conclusion that many
encountered this, but no-one found a solution.
If I remember correctly,