I've tried, whenever possible not to lie to the server about the client
configuration. However, there are now multiple cases where a GlobalProtect
server responds with a misleading error when the `ssl-vpn/login.esp` request
doesn't
contain the exact, magic value of `clientos=Windows`.
* https://
Thanks for the gist, making definite progress. Pulse now connects
through mitmdump's proxy. I get some basic logging in the console, but the /tmp
dir does not contain any logs using the command in the gist (substituting my
Pulse Secure endpoint of course).
Any ideas?
On Tue, 2018-09-04 at 05:5
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 fly
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, wh
