cancel
Showing results for 
Search instead for 
Did you mean: 

PulseSecure client not working on kernel 4.18

Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

Thank you so much for your kindly attention.

Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

Hi, any news about a new client release?

 

Regards,

Antonio Petricca

New Contributor

Re: PulseSecure client not working on kernel 4.18

This is becomming very urgent, please update about the statuse.

Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

What version of Linux are you using? I am on 4.19.15-300 (Fedora 29) all is well.


I have upgraded from 27+ to 29. I have gone through quite a process to get this to work in the past.

Check out these form links. Maybe something here will allow you to get it working?

Fedora 27 workaround.

Fedora 28 Workaround.


Highlighted
New Contributor

Re: PulseSecure client not working on kernel 4.18

Hi,

I'm using Fedora release 29, kernel: 4.19.13-300.fc29.x86_64
Tried with ps-pulse-linux-9.0r1.0-b739-centos-rhel-64-bit-installer.rpm

# rpm -qa | grep compat-libicu
compat-libicu60-60.2-2.fc29.x86_64

 

According to logs it fails on HC policy check.

 
$ strace /usr/local/pulse/pulsesvc -h vpn-host.com -u username -U https://vpn-host.com/ -r "RSA Token"

....
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f255ae56a10) = 5631
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x557a4a12db70, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f255ae915c0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f255ae915c0}, 8) = 0
wait4(-1,
Segmentation fault (core dumped)

 

Logs from ~/.pulse_secure/pulse/pulsesvc.log

...
20190130153002.980833 pulsesvc[p5608.t5608] pulsesvc.info sending HC tnc update message to IVE (HostCheckerLinuxTNCC.cpp:336) 20190130153003.36275 pulsesvc[p5608.t5608] dsssl.info verify_server_cert_callback : Certificate verification - Successful (DSSSLSock.cpp:1577) 20190130153003.36333 pulsesvc[p5608.t5608] dsssl.info verify_server_cert_callback : Certificate verification - Successful (DSSSLSock.cpp:1577) 20190130153003.36629 pulsesvc[p5608.t5608] dsssl.info verify_server_cert_callback : Certificate verification - Successful (DSSSLSock.cpp:1577) 20190130153003.62797 pulsesvc[p5608.t5608] pulsesvc.info extracting Tnc payload (HostCheckerLinuxTNCC.cpp:261) 20190130153003.62870 pulsesvc[p5608.t5608] pulsesvc.info ConnID: 2 (HostCheckerLinuxTNCC.cpp:272) 20190130153003.62947 pulsesvc[p5608.t5608] pulsesvc.info Delivering message to IMCid: 0, message_size: 3868 (HostCheckerLinuxTNCC.cpp:362) 20190130153003.62977 pulsesvc[p5608.t5608] pulsesvc.info Extracting rule properties (HCLinuxImc.cpp:276) 20190130153003.63005 pulsesvc[p5608.t5608] pulsesvc.info Extracting rule properties (HCLinuxImc.cpp:276) 20190130153003.63059 pulsesvc[p5608.t5608] pulsesvc.info Adding Process Rule for policy: vc0|4237|policy_3|3|ClamAV_antivirus (HCLinuxImc.cpp:383) ... 20190130153003.63895 pulsesvc[p5608.t5608] pulsesvc.info Extracting rule properties (HCLinuxImc.cpp:276) 20190130153003.63912 pulsesvc[p5608.t5608] pulsesvc.info Received Policy Data Rule for policy: vc0|4237|policy_4|3|McAfee_port_default (HCLinuxImc.cpp:391) 20190130153003.63922 pulsesvc[p5608.t5608] pulsesvc.info Successfully setup the HC policy (HCLinuxImc.cpp:396) 20190130153003.63931 pulsesvc[p5608.t5608] pulsesvc.info Successfully extracted the policy data (HCLinuxImc.cpp:131) 20190130153003.63942 pulsesvc[p5608.t5608] pulsesvc.info Evaluating the HC policy, polName: vc0|4237|policy_3|3|ClamAV_antivirus (HCLinuxImc.cpp:418)