Package Details: pulse-secure 9.1r11.0_b6725-1

Git Clone URL: https://aur.archlinux.org/pulse-secure.git (read-only, click to copy)
Package Base: pulse-secure
Description: Pulse Connect Secure (PCS) Client
Upstream URL: https://www.pulsesecure.net/
Licenses: custom
Conflicts: pulse-connect-secure
Submitter: yan12125
Maintainer: chiwanpark
Last Packager: chiwanpark
Votes: 27
Popularity: 3.37
First Submitted: 2017-09-02 07:40
Last Updated: 2021-02-24 10:18

Pinned Comments

chiwanpark commented on 2021-02-24 10:21

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.

yan12125 commented on 2018-10-30 11:41

You need to rebuild webkitgtk if you got ICU related errors.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

tomek2102 commented on 2021-03-04 05:51

@chiwanpark Yes, I have started it.

chiwanpark commented on 2021-03-04 05:48

@tomek2102 did you start the service named 'pulsesecure'? 9.1R11 requires the service. you need to start the service before running the client.

tomek2102 commented on 2021-03-04 05:29

Hi, I'm trying to get it working too but I have following problem:

DBUS api call failed with code: 2 - message:GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.psecure.pulse was not provided by any .service files

The UI sometimes starts but I cannot create connection and connect. I have created dir and symlink but without any change. What can be wrong? The client version between last November and December was working OK.

newnumbertwo commented on 2021-03-02 22:44

After reading thecrow's comments I created the missing /var/lib/pulsesecure/pulse directory:

$ sudo mkdir -p /var/lib/pulsesecure/pulse

and created a symlink:

$ sudo ln -s /etc/ca-certificates/extracted/ca-bundle.trust.crt /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt

and now I am able to connect, so some might attempt these steps before reverting.

I also did not need to restart the pulsesecure service, pulselauncher worked after the symlink and directory were created.

I extracted the RPM spec file from pulsesecure-9.1-R11.x86_64.rpm using rpmrebuild and found that:

$ mkdir -p /var/lib/pulsesecure/pulse

was in the %post section of the extracted SPEC but is not in the PKGFILE. The symlink needs to be created because this is where redhat/centos/etc distros store CA bundles, and thus where the pulse package expects it to be, as evidenced by running strings on the pulselauncher binary and grepping for .crt:

$  strings /opt/pulsesecure/bin/pulselauncher | grep "[.]crt"
/etc/ssl/certs/ca-certificates.crt
/etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt

abyss02 commented on 2021-02-26 08:27

@thecrow:

THAT was really really helpful, thanks a lot. Now, my pulse client works like a charm ...

thecrow commented on 2021-02-26 07:24

@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.

abyss02 commented on 2021-02-25 17:17

Ok, installed the new 9.1R11 and ran systemctl enable pulsesecure && systemctl start pulsesecure - afterwards restarted arch:

So,

  1. pulseUI works
  2. adding a connection works
  3. connecting works

but ...

  1. i always get a cert warning, although i imported the needed ca with trust anchor an so on ... (but this is probably my problem)

BUT ...

  1. if the pulsesecure.service is restarted, the gui looses all the connections ... that is weird.

Any ideas?

Regards, A.

je-vv commented on 2021-02-25 05:38

@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...

chiwanpark commented on 2021-02-24 10:22

@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.

chiwanpark commented on 2021-02-24 10:21

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.