About Mish

Mish · ‎01-20-2016

I want to start using Host Checker for the first time but it appears that if I enable it I need to have a policy for all platforms in order for the connection to succeed. For example: Most/All of our users are Windows users. I want to use Host Checker to check for the existence of a file as a rudimentary way to verify that someone hasn't installed the Pulse Secure client on their home PC are VPNing from home. They should only be using their employer provided laptop. If I create a Host Checker policy for Windows but not for any other platforms then they few users that are using other OSes cannot connect. Is there a way around this?

Mish · ‎01-20-2016

Is there an alternative or workaround for people that want to use Pulse Client 5.2+ with SRX? I was actually planning to implement this for a disaster recovery scenario where I wouldn't install a full blown PCS.

Mish · ‎01-20-2016

I am very interested in being able to control on the server-side ciphersuite order to suggest that my clients use PFS ciphersuites first before resorting to non-PFS. I tried to contact my PulseSecure Sales Engineer (That was news to me that I had one) to submit a feature request but I don't get a response. For now I'd like to know if I can log which cipher suite was negotiated.

Mish · ‎01-20-2016

Based on the comments it seems like you need to hardcode credentials. That's not as useful as an HTML5 client that can prompt for credentials regardless of client OS. Am I correct in this is how it works?

Host Checker for some OSes and not others in the s...

Re: Juniper owners, how to get client?

Re: Allow changing cipher order

Re: HTML5 RDP Client in 8.2?