Package Details: pulse-secure 9.0r3.0_b923-1

Git Clone URL: https://aur.archlinux.org/pulse-secure.git (read-only)
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: 14
Popularity: 0.296703
First Submitted: 2017-09-02 07:40
Last Updated: 2019-01-31 15:00

Pinned Comments

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 »

chiwanpark commented on 2019-03-26 13:35

@hkirsman You can use pulse-secure without webkitgtk via pulsesvc command. As described as in dependencies section, webkitgtk is required only for pulseUi frontend, not entire pulse-secure client.

hkirsman commented on 2019-03-26 06:58

To get pulseUi working I also had to install webkitgtk (something that has been mentioned below also). Wondering why it's not dependency of this package? May be there's even some better one because webkitgtk took quite a while to compile.

yan12125 commented on 2018-12-01 01:41

Dropped - I switched to openconnect to connect to Pulse Secure servers.

yan12125 commented on 2018-10-30 11:41

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

igor1982 commented on 2018-10-30 10:53

PulseUi doesn't work because it depends on the icu package in version 62, but icu has been updated to 63.

The error I got is

pulseUi: error while loading shared libraries: libicui18n.so.62: cannot open shared object file: No such file or directory

Is there any way out except for downgrading icu?

hirunatan commented on 2018-10-11 12:54

Hello. I'm getting this error after successful login with pulseUi:

(pulseUi:9418): Gtk-ERROR **: 14:37:32.588: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
`trap' para punto de parada/seguimiento

I don't understand how could there be symbols of GTK 2 and GTK 3 in the same executable. Any clue of what to investigate or how to solve this?

Thanks

je-vv commented on 2018-09-30 02:29

Currently using the "OATH Passcode" realm on the pulsesvc command line. Anyone has successfully attempted the "Class-A DigitalBadge" realm with pulsesvc, which requires a certificate? Upon executing "pulsescv --help" I see no way to specify a cert, and if using the the "Class-A DigitalBadge" realm doesn't prompt for a cert either. Thanks !

yan12125 commented on 2018-09-07 13:03

@kikislater: thanks for the patch! I've applied a simplified version and PulseClient should work now.

yan12125 commented on 2018-09-07 13:03

9.0r2.0_b1151 is out. Please leave a comment if you found a mirror. This version should be released as soon as possible as it contains security fixes [1].

[1] https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA43877/?l=en_US&atype=sa&fs=Search&pn=1&atype=sa

kikislater commented on 2018-09-06 12:04

Ok thank you, pulsesvc works ! Someone patch it with older version : https://github.com/kaymmm/pulseconnectsecure-arch Don't need it at this time since pulsesvc works ...