Arch Linux User Repository

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.

I tried this package and compiled webkitgtk, when I try to execute pulseUi I get a segmentation fault (core dumped) pulseUi error.

Is anyone else experiencing this problem?

BTW @SJrX, I just tried with my laptop totally up to date, both from official repos and AUR, and everything worked out just fine, no need to rebuild webkitgtk. The last change on webkitgtk (https://aur.archlinux.org/cgit/aur.git/log/?h=webkitgtk "Patching for build with icu 68.2") was precisely about adding a "68.2" icu patch. Not sure, if from 10 days ago to Today, some libs might have changed preventing webkitgkt to build again, but around those 10 days ago, building it had no issues. Perhaps you could try the binary as well.

I'll be posting something about migrating to webkit2gtk on the pulse-secure forums, but it seems no devs pay attention to that. I have no clue why on earth pulse-secure still depends on webkit1 for webui support... I'll also be posting about how to accomplish webui MFA from the command line, to see if the users have gotten that solved, and stop using obsolete webkitgtk...

@SJrX, I see, I haven't had to rebuild webkitgtk since its last rebuilt needed like a week and a couple of days more ago. I'll just try it again. But your backporting solutions looks fine to me. Actually at least the curl one seems like a good temporal work around that could be implemented in this same pulse-secure package, while upstream fixes the curl issue.

@je-vv at the moment, webkitgtk can't be rebuilt is my understanding, and my thing failed today. I didn't try with webkitgtk-bin.

I can't speak to anything about changing the internal package, I am doing a hack just to work around the issue. If people more knowledgable than me want to use it, then all the better :)

@SJrX, according to the pinned messages, on both pulse-secure and webkitgtk, the icu version change, only requires webkitgtk to rebuild, no need to backport icu, or revert it. Tough I agree rebuilding takes a huge amount of time. I'd love to stop needing the pulse-secure GUI just for MFA. The curl issue though, does require wether backporting or reverting curl. BTW, I like your backporting solution, and I'm wondering if that could be incorporated temporally (while there's no new pulse-secure version with the fix to work with newest curl), into the pulse-secure AUR package itself, not as a directory in $HOME, but rather being part of "/usr/local/pulse". Notice /usr/bin/pulseUi wouldn't need any modification, since it already modifies LD_LIBRARY_PATH accordingly, but /usr/bin/pulsesvc might need to be moved to "/usr/local/pulse", and a bash or shell wrapper (/usr/bin/pulsesvc_wrapper) is needed around it, changing LD_LIBRARY_PATH in it.

Perhaps @yan12125 or @chiwanpark can take a look. But at any rate, for the curl issue, I'd recommend users to push to the pulse-secure company, since they are the ones to finally fix the issue.

Moreover, if the company (upstream) is also pushed to use webkit2gtk, rather than the old obsolete and insecure webkitgtk, that would be much better...

So I had two issues that prevented this from working today. The first is that icu (https://archlinux.org/packages/core/x86_64/icu/) has been upgraded, the second is the curl issues with 7.74, in previous comments.

icu and especially curl have lots of dependencies so it didn't seem smart to downgrade them. What I did was I found the previous archives, and unzipped them somewhere, then used LD_LIBRARY_PATH to use the old versions. You can get the old versions from the Arch Linux Archive, here are some examples.

mkdir -p ~/old_versions cd ~/old_versions wget https://archive.archlinux.org/packages/c/curl/curl-7.73.0-1-x86_64.pkg.tar.zst wget https://archive.archlinux.org/packages/i/icu/icu-67.1-1-x86_64.pkg.tar.zst

At this point you should validate the signatures for the packages.

Then unarchive them: tar -I zstd -xvf curl-7.73.0-1-x86_64.pkg.tar.zst tar -I zstd -xvf icu-67.1-1-x86_64.pkg.tar.zst

Then export LD_LIBRARY_PATH=/home/<username>/old_versions/usr/lib/:$LD_LIBRARY_PATH

then ran pulseUi and it worked.

CC @je-vv

@Hubro, I see your comment on https://aur.archlinux.org/packages/webkitgtk/#comment-784272, however, strangely enough, it built for me, with its latest change ~10 days ago... I do prefer building it, but have you tried using the binary AUR package (https://aur.archlinux.org/packages/webkitgtk-bin)? That might prevent building issues I'd guess..

I do have to use webkitgtk, since I have no clue how to use pulse-secure with MFA on the command line, and that's a must where I work unfortunately, :( However if you don't use the multi factor authentication, and use an OTP instead, or similar non multi factor auth, then you can get away with using the pulse-secure command line. I used it for several years, without even having webkitgtk installed... An usage example:

pulsesvc -h ${GATEWAY} -u ${USER} -p ${OATH_PIN_PASS} -r "OATH Passcode"

But it all depends on what the org needing you to use this privative SW requires...

I'm no longer able to use this package since AUR's webkitgtk package will no longer compile. Does anybody else have this issue? Is there a workaround that avoids using the AUR webkitgtk package? Or have any of you succeeded in building it?

@chiwanpark: There's a newer version, 9.1.R10. But it seems it hasn't been updated for the trial downloads.

@lindbergio yes, they rewrote the application and released it as 9.1r9.0_b4983. however, b4983 also crashes with curl 7.74.