BTW, on all 3 posts under the pulse-secure comuniy forum where I'm involved, the answer is always to get a big shot on business relations with pulse-secure, to get in contact with them. So I guess there won't be any support from pulse-secure to final users on the issues their own SW generates. There's NO way to reach out to their devs or support team. I don't have any alternative, given the company where I work chose pulse-secure and uses MFA even requiring its GUI, which depends on obsolete and insecure webkitgtk.
I guess the work around with curl-pulse-secure is all there will be, until everything starts segfaulting on other platforms with more users, like redhat derivatives and debian/ubuntu derivatives, which can influence big shots from IT making business with them. That's to be expected from closed source SW I'd guess... How disappointing !!
Pinned Comments
chiwanpark commented on 2021-02-24 10:21 (UTC)
If you want to use old pulse-secure client 9.1r9, please download the following package.
https://drive.google.com/file/d/1_8tRA-T9vV08n_TpHqdcG5IvalxBuZ7_/view?usp=sharing
The rewritten pulse-secure client requires a service called 'pulsesecure'. Please enable and start the service before running the client.