Package Details: pulse-secure 22.7r3.0_b30227-1

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: 34
Popularity: 0.090566
First Submitted: 2017-09-02 07:40 (UTC)
Last Updated: 2024-10-10 14:26 (UTC)

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.

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 27 Next › Last »

<deleted-account> commented on 2021-02-06 11:04 (UTC)

hey, can you please provide the new client 9.1.R10, you can find it here: https://vubnet.vub.ac.be/downloads.html

je-vv commented on 2021-02-06 03:57 (UTC)

Do we need a service to start puilse-secure now? Ohh boy... But I don't think the seg faulting using the backported libs, are due to that, do you @chiwanpark?

BTW, I don't think I can test any time soon then, if systemd is required, since I use Artix, so I'd need to port the service to S6, which is the init+supervisor system I use. So if the package moves to a newer release (I see it worked for @mattonthehill) I'll have to stick with the 7.73.0, until porting the service, or finding a work around by using openconnect somehow. I understand openconnect doesn't handle pulse MFA, but perhaps some people out there is doing magic with it...

chiwanpark commented on 2021-02-06 03:41 (UTC)

@mattonthehill: Thanks for your testing. :)

@je-vv: from 9.1R10, you need to start pulsesecure.service via sudo systemd start pulsesecure.service. The message 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 is shown because the service is not running.

I will automatically enable the service after updated package. Thanks for reporting.

je-vv commented on 2021-02-06 03:29 (UTC)

@thecrow, I don't know what else to put in there, they don't accept the fact the package got broken.

@chiwanpark, I tested the binary package you made available with 9.1r10.0_b5655, without reverting curl, neither changing LD_LIBRARY_PATH, and it just seg faults without any output:

% /opt/pulsesecure/bin/pulseUI
Segmentation fault

And by using the backported libraries provided by curl-pulse-secure thorough LD_LIBRARY_PATH, it still seg faults, though the gui shows up for a bit less than a second:

% export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/usr/local/pulse"
% /opt/pulsesecure/bin/pulseUI
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 
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 
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 
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 
Segmentation fault

So now, things look way worse than before, because it seg fauls no matter if using the backported libraries or not...

Running without backported libs with gdb shows:

% gdb /opt/pulsesecure/bin/pulseUI
...
Reading symbols from /opt/pulsesecure/bin/pulseUI...
(No debugging symbols found in /opt/pulsesecure/bin/pulseUI)
(gdb) run
Starting program: /opt/pulsesecure/bin/pulseUI 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff09aff7e in __strcmp_avx2 () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff09aff7e in __strcmp_avx2 () at /usr/lib/libc.so.6
#1  0x00007ffff12dacbb in lh_insert () at /opt/pulsesecure/lib/dsOpenSSL/libcrypto.so
#2  0x00007ffff123c994 in OBJ_NAME_add () at /opt/pulsesecure/lib/dsOpenSSL/libcrypto.so
#3  0x00007fffeca0e021 in  () at /usr/lib/libssl.so.1.1
#4  0x00007ffff7f7918f in __pthread_once_slow () at /usr/lib/libpthread.so.0
#5  0x00007fffec8e54ea in CRYPTO_THREAD_run_once () at /usr/lib/libcrypto.so.1.1
#6  0x00007fffeca0e224 in OPENSSL_init_ssl () at /usr/lib/libssl.so.1.1
#7  0x00007fffecb40731 in  () at /usr/lib/libcurl.so.4
#8  0x00007fffecaf3735 in  () at /usr/lib/libcurl.so.4
#9  0x00007ffff7fe12de in call_init.part () at /lib64/ld-linux-x86-64.so.2
#10 0x00007ffff7fe13c8 in _dl_init () at /lib64/ld-linux-x86-64.so.2
#11 0x00007ffff098d0e5 in _dl_catch_exception () at /usr/lib/libc.so.6
#12 0x00007ffff7fe5705 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#13 0x00007ffff098d088 in _dl_catch_exception () at /usr/lib/libc.so.6
#14 0x00007ffff7fe4f3e in _dl_open () at /lib64/ld-linux-x86-64.so.2
#15 0x00007ffff7f6334c in  () at /usr/lib/libdl.so.2
#16 0x00007ffff098d088 in _dl_catch_exception () at /usr/lib/libc.so.6
#17 0x00007ffff098d153 in _dl_catch_error () at /usr/lib/libc.so.6
#18 0x00007ffff7f63b89 in  () at /usr/lib/libdl.so.2
#19 0x00007ffff7f633d8 in dlopen () at /usr/lib/libdl.so.2
#20 0x00007fffed1161ac in  () at /usr/lib/libdw.so.1
#21 0x00007ffff7fe12de in call_init.part () at /lib64/ld-linux-x86-64.so.2
#22 0x00007ffff7fe13c8 in _dl_init () at /lib64/ld-linux-x86-64.so.2
#23 0x00007ffff7fd20ca in _dl_start_user () at /lib64/ld-linux-x86-64.so.2
#24 0x0000000000000001 in  ()
#25 0x00007fffffffdbde in  ()
#26 0x0000000000000000 in  ()

So there you go, there are still issues with the curl library...

And doing the same using LD_LIBRARYPATH with the backported curl libraries:

% gdb /opt/pulsesecure/bin/pulseUI
...
Reading symbols from /opt/pulsesecure/bin/pulseUI...
(No debugging symbols found in /opt/pulsesecure/bin/pulseUI)
(gdb) run
Starting program: /opt/pulsesecure/bin/pulseUI 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffec007640 (LWP 7998)]
[New Thread 0x7fffeb806640 (LWP 7999)]
[New Thread 0x7fffeaec0640 (LWP 8000)]
[New Thread 0x7fffec0a6a40 (LWP 8001)]
[New Thread 0x7fffea6bf640 (LWP 8003)]
[New Thread 0x7fffe9ebe640 (LWP 8004)]
[New Thread 0x7fffe88da640 (LWP 8005)]
[New Thread 0x7fffd3fff640 (LWP 8006)]
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 
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 
[Thread 0x7fffe88da640 (LWP 8005) exited]
[Thread 0x7fffd3fff640 (LWP 8006) exited]
[New Thread 0x7fffd3fff640 (LWP 8007)]
[Thread 0x7fffe9ebe640 (LWP 8004) exited]
[Thread 0x7fffea6bf640 (LWP 8003) exited]
[New Thread 0x7fffea6bf640 (LWP 8010)]
[New Thread 0x7fffe9ebe640 (LWP 8011)]
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 
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 

Thread 11 "pulseUI" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea6bf640 (LWP 8010)]
0x00007ffff09b7ee1 in __memset_avx2_erms () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff09b7ee1 in __memset_avx2_erms () at /usr/lib/libc.so.6
#1  0x0000555555554ccc in  ()
#2  0x0000555555550495 in GetDSAccessServiceInterface(pincGuid const&, unsigned int, void**) ()
#3  0x0000555555550586 in DSAccessGetPluginInterface(char const*, pincGuid const&, unsigned int, void**) ()
#4  0x000055555551bb3e in DialogManager::InitiateJUNS() ()
#5  0x000055555552436f in DialogManager::OnJamTimer(unsigned int) ()
#6  0x0000555555507c1b in CJamCommandListProcessor::OnJamTimer(unsigned int) ()
#7  0x00007ffff7f5d63c in  () at /usr/lib/librt.so.1
#8  0x00007ffff7f713e9 in start_thread () at /usr/lib/libpthread.so.0
#9  0x00007ffff0952293 in clone () at /usr/lib/libc.so.6

Then there are issues with glibc...

And the community forum seems totally useless to me, as well as the comments some of those guys have included in the github issue... Whether saying got get support with a big shot guy doing business with them, or just install a newer version, which is just as useless, when never getting to debug what's broken. It's really tiresome to try arguing with them.

mattonthehill commented on 2021-02-05 20:36 (UTC)

Thanks for your package @chiwanpark - I managed to connect to my workplace's VPN, after the following steps:

  • Install curl-pulse-secure;
  • Start the pulsesecure service;
  • Run PulseUI with "LD_LIBRARY_PATH=/usr/local/pulse pulseUI"

It still complains quite a lot, but it worked and let me set up a connection. Thanks again!

thecrow commented on 2021-01-26 12:59 (UTC)

@chiwanpark,@je-vv Podeis actualizar la información que solicitan desde el foro de pulse secure, para replicar el problema con curl 7.74

je-vv commented on 2021-01-23 22:56 (UTC)

@chiwanpark, although 9.1R10 does not fix the curl related segfault, I see it positive if you update the package any ways. Thanks a lot !

je-vv commented on 2021-01-23 22:53 (UTC)

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 !!

tryax commented on 2021-01-21 09:46 (UTC)

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

lib32-icu has been updated to 68.2-1, so pulse can't find version 67?

chiwanpark commented on 2021-01-19 15:46 (UTC)

@je-vv: the 9.1R10 does not fix the curl related crash. I guess that the user posting 9.1R10 works with curl 7.74 in Ubuntu did test with OpenSSL < 1.1.0. I've posted the question about OpenSSL version to the forum.

https://community.pulsesecure.net/t5/Pulse-Desktop-Clients/Linux-Pulse-Client-does-not-work-with-curl-7-74/m-p/44607/highlight/true#M2253