Who rated this post

Confirming, R82 jumbo 60 still has the 2038 issue:

[Expert@DallasSC]# cpinfo -y fw1

This is Check Point CPinfo Build 914000259 for GAIA
[FW1]
	HOTFIX_R82_JUMBO_HF_MAIN	Take:  60
	HOTFIX_NGM_DOCTOR_AUTOUPDATE
	HOTFIX_PUBLIC_CLOUD_CA_BUNDLE_AUTOUPDATE
	HOTFIX_WEBCONSOLE_AUTOUPDATE
	HOTFIX_VCE_R81_20_AUTOUPDATE
	HOTFIX_INEXT_NANO_EGG_AUTOUPDATE
	HOTFIX_GOT_MGMT_AUTOUPDATE
	HOTFIX_GOT_TPCONF_MGMT_AUTOUPDATE

FW1 build number:
This is Check Point Security Management Server R82 - Build 009
This is Check Point's software version R82 - Build 013

[Expert@DallasSC]# date +%s -d"Jan 19, 2038 03:14:07Z"
2147483647

[Expert@DallasSC]# date +%s -d"Jan 19, 2038 03:14:08Z"
date: invalid date 'Jan 19, 2038 03:14:08Z'

Looks like R82.10 switches to 64-bit time_t:

[Expert@SomeFirewall]# cpinfo -y fw1

This is Check Point CPinfo Build 914000224 for GAIA
[FW1]
	HOTFIX_INEXT_NANO_EGG_AUTOUPDATE
	HOTFIX_UCA_SSH_TUNNELING_SERVICE_AUTOUPDATE
	HOTFIX_UCA_SSH_TUNNELING_APP_AUTOUPDATE
	HOTFIX_UCA_INFRA_MONITOR_SERVICE_AUTOUPDATE
	HOTFIX_UCA_INFRA_LOG_SERVICE_AUTOUPDATE
	HOTFIX_UCA_INFRA_AUTOUPDATE
	HOTFIX_PUBLIC_CLOUD_CA_BUNDLE_AUTOUPDATE
	HOTFIX_GOT_TPCONF_AUTOUPDATE

FW1 build number:
This is Check Point's software version R82.10 - Build 767
kernel: R82.10 - Build 768

[Expert@SomeFirewall]# date +%s -d"Jan 19, 2038 03:14:07Z"
2147483647

[Expert@SomeFirewall]# date +%s -d"Jan 19, 2038 03:14:08Z"
2147483648

[Expert@SomeFirewall]# date +%s -d"Jan 19, 20380 03:14:08Z"
580965016448