@thecrow:
THAT was really really helpful, thanks a lot. Now, my pulse client works like a charm ...
Git Clone URL: | https://aur.archlinux.org/pulse-secure.git (read-only, click to copy) |
---|---|
Package Base: | pulse-secure |
Description: | Ivanti Secure Access Client |
Upstream URL: | https://www.pulsesecure.net/ |
Licenses: | custom |
Conflicts: | pulse-connect-secure |
Submitter: | yan12125 |
Maintainer: | chiwanpark |
Last Packager: | chiwanpark |
Votes: | 36 |
Popularity: | 0.49 |
First Submitted: | 2017-09-02 07:40 (UTC) |
Last Updated: | 2025-02-18 11:56 (UTC) |
« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 27 Next › Last »
@thecrow:
THAT was really really helpful, thanks a lot. Now, my pulse client works like a charm ...
@abyss02
To resolve the certificate warning, pulsesecure will look for the certificate authorities in the path /etc/pki/ca-trust/extracted/openssl, add the symbolic link:
/etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt -> /etc/ca-certificates/extracted/ca-bundle.trust.crt
The connections are saved in /var/lib/pulsesecure/pulse
, you have to create the directory so that pulsesecure can save them and they are not lost when restarting the service.
Ok, installed the new 9.1R11 and ran systemctl enable pulsesecure && systemctl start pulsesecure - afterwards restarted arch:
So,
but ...
BUT ...
Any ideas?
Regards, A.
@chiwanpark thanks for keeping the old package available at least through drive. I can't use new versions if they keep depending on systemd. I notice the service just calls another script, and I tried:
sudo /opt/pulsesecure/bin/startup.sh start
To then execute:
/opt/pulsesecure/bin/pulseUI
But even by doing so, I can't add new connections, neither connect...
If someone finds a way to make pulse-secure work without systemd, please let me know. It might require several calls, as I was trying, no problem... Not sure if I'd need to call some dbus stuff, which I'm not familiar with...
For now I need to keep using the old 9.1.r9 version with the curl-pulse-secure package...
@abyss02 I've updated the package to new version 9.1r11. It seems that the curl problem disappears. However, the host checker still does not work properly.
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.
@je-vv, you could probably make it work without systemd. The systemd control file makes a call to a simple shell script with "do_start" and "do_stop" functions to run/kill a binary, so I expect it could be made compatible with non-systemd systems.
Hey there, there is a new version 9.1R11 with this changelog:
It can be downloaded here: https://www.rz.uni-osnabrueck.de/fileadmin/user_upload/VPN/Software/ps-pulse-linux-9.1r11.0-b6725-64-bit-installer.rpm
Seems that they had some issues with host checker.
Will you give it another try? Or could you please provide the PKGBUILD of your 9.1R10-Package?
Regards, A.
I downloaded the latest version 9.1R11, after manually copying the files over version 9.1R10, the VPN is established, it already works with curl 7.75.
@treizeku, you moved way back, to 9.1r8.0_b165 actually, while current version is 9.1r9.0_b255. Those old versions don't require any service, you just call the pulsesvc for command line or you just call the pulseUI binary for the gui... That was the old model... However not sure why 9.1r9.0_b255 is not working for you. I'd guess the really new one, on the GDrive provided by @chiwanpark is the one having some future, and it's pending solving some issues prior to releasing, but not so bright at least for me, since it depends on loading a systemd service it seems...
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.