> Source: [sk92568](https://support.checkpoint.com/results/sk/sk92568) # sk92568 - New law in Israel regarding Daylight Savings Time 2013 | Property | Value | |----------|-------| | Solution ID | sk92568 | | Date Created | 2013-03-22 | | Last Modified | 2023-03-23 | | Technical Level | General | | Products | Security Gateway, Security Management Server, Multi-Domain Security Management Server | | Versions | R82.10, R82, R81.20, R82.20 | | OS | Gaia | ## Symptoms - There is a new law in Israel regarding Daylight Savings Time 2013 (). ## Cause The old Time Decree Law, since 2005 until March 2013 stated the following: Israel's Daylight Savings Time begins on the last Friday before April, 2 at 2:00AM and will end on the last Sunday before the tenth day of the Hebrew month of Tishrei at 2:00AM. [The new Time Decree Law states](http://en.wikipedia.org/wiki/Israel_Summer_Time#2013.E2.80.93Present): On November 5, 2012, the Israeli Knesset approved the bill to extend IDT to a period of 193 days (instead of 185). As of 2013: * DST starts at 02:00AM on the Friday before the last Sunday of March. * DST ends at 02:00AM on the first Sunday after October 1, unless it occurs on the second day of the Jewish Rosh HaShana holiday (Jewish New Year), in which case DST ends a day later (i.e., at 02:00 the first Monday after October 2). On July 8, 2013, the Israeli Knesset approved the bill to extend IDT even further: * IDT start at 02:00AM on the Friday before the last Sunday of March. * IDT ends at 02:00AM on the last Sunday of October. ## Solution This problem was fixed. The fix is included in: * [Check Point R77.10](http://supportcontent.checkpoint.com/solutions?id=sk97617) * [Check Point R76SP.10 for 61000/41000](http://supportcontent.checkpoint.com/solutions?id=sk102788) * [Check Point R76SP.20 for 61000/41000](http://supportcontent.checkpoint.com/solutions?id=sk105938) Check Point recommends to always upgrade to the most recent version ([upgrade Security Gateway](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=73) / [upgrade VSX](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=359) / [upgrade Security Management Server](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=184) / [upgrade Multi-Domain Security Management Server](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=166)). For **lower [supported](http://www.checkpoint.com/support-services/support-life-cycle-policy/enterprise-software-support-timeline/index.html) versions** , Check Point can supply a **Hotfix** . [Contact Check Point Support](http://www.checkpoint.com/services/contact/index.html) to get a Hotfix for this issue. A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix. For faster resolution and verification, please collect [CPinfo file](http://supportcontent.checkpoint.com/solutions?id=sk92739) from all involved machines. Check Point offers hotfix based on [**Time Zone Data v. 2013d**](http://mm.icann.org/pipermail/tz-announce/2013-July/000012.html) (released on 05 July 2013): * For **SecurePlatform OS** * For **Gaia OS** * For **IPSO 6.2 OS** *** ** * ** *** **Procedure:** * Hotfix for SecurePlatform OS {#SecurePlatform} ---------------------------------------------- **Notes:** This hotfix is suitable for the following versions: * SecurePlatform R65 HFA_60 * SecurePlatform R65 HFA_70 * SecurePlatform R71.30 * SecurePlatform R71.40 * SecurePlatform R71.50 * SecurePlatform R75 * SecurePlatform R75.10 * SecurePlatform R75.20 * SecurePlatform R75.30 * SecurePlatform R75.40 * SecurePlatform R75.40VS * SecurePlatform R75.45 * SecurePlatform R75.46 * SecurePlatform R75.47 * SecurePlatform R76 **Hotfix installation instructions:** 1. Hotfix has to be installed only on SecurePlatform-based machine (Security Gateway / Security Management Server / Multi-Domain Management Server). 2. Transfer the hotfix package to the machine (e.g., into `/some_path_to_fix/`). 3. Make sure that symbolic link `/etc/localtime` points to `/usr/share/zoneinfo/Asia/Jerusalem` file: **`[Expert@HostName]# file /etc/localtime`** Output should be: ``/etc/localtime: symbolic link to `/usr/share/zoneinfo/Asia/Jerusalem'`` 4. Check the current DST: **`[Expert@HostName]# /usr/sbin/zdump -v Asia/Jerusalem | grep `** Example for year 2013: > > ``` > [Expert@HostName]# /usr/sbin/zdump -v Asia/Jerusalem | grep 2013 > Asia/Jerusalem Thu Mar 28 23:59:59 2013 UTC = Fri Mar 29 01:59:59 2013 IST isdst=0 gmtoff=7200 > Asia/Jerusalem Fri Mar 29 00:00:00 2013 UTC = Fri Mar 29 03:00:00 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Sep 7 22:59:59 2013 UTC = Sun Sep 8 01:59:59 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Sep 7 23:00:00 2013 UTC = Sun Sep 8 01:00:00 2013 IST isdst=0 gmtoff=7200 > ``` 5. Hardware clock should already be in UTC: **`[Expert@HostName]# hwclock --utc`** 6. Install the hotfix: * SecurePlatform version R75.40 only: **`[Expert@HostName]# cd /some_path_to_fix/`** **`[Expert@HostName]# tar -zxvf SecurePlatform_HOTFIX_FOXX_HF_HA40_606.tgz`** **`[Expert@HostName]# ./SecurePlatform_HOTFIX_FOXX_HF_HA40_606_`*BUILD*** * SecurePlatform all versions (listed above) other than R75.40: **`[Expert@HostName]# cd /some_path_to_fix/`** **`[Expert@HostName]# rpm -Uhv --force --nodeps tzdata-2009f-1.986606001cp.noarch.rpm `**

7. Verify that DST was changed: **`[Expert@HostName]# /usr/sbin/zdump -v Asia/Jerusalem | grep `** Example for year 2013: > > ``` > [Expert@HostName]# /usr/sbin/zdump -v Asia/Jerusalem | grep 2013 > Asia/Jerusalem Thu Mar 28 23:59:59 2013 UTC = Fri Mar 29 01:59:59 2013 IST isdst=0 gmtoff=7200 > Asia/Jerusalem Fri Mar 29 00:00:00 2013 UTC = Fri Mar 29 03:00:00 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Oct 26 22:59:59 2013 UTC = Sun Oct 27 01:59:59 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Oct 26 23:00:00 2013 UTC = Sun Oct 27 01:00:00 2013 IST isdst=0 gmtoff=7200 > ```



* Hotfix for Gaia OS {#Gaia} -------------------------- **Notes:** This hotfix is suitable for the following versions: * Gaia R75.40 * Gaia R75.40VS * Gaia R75.45 * Gaia R75.46 * Gaia R75.47 * Gaia R76 **Hotfix installation instructions:** 1. Hotfix has to be installed only on Gaia-based machine (Security Gateway / Security Management Server / Multi-Domain Management Server). 2. Transfer the hotfix package to the machine (e.g., into `/some_path_to_fix/`). 3. Make sure that symbolic link `/etc/localtime` points to `/usr/share/zoneinfo/Asia/Jerusalem` file: **`[Expert@HostName]# file /etc/localtime`** Output should be: ``/etc/localtime: symbolic link to `/usr/share/zoneinfo/Asia/Jerusalem'`` 4. Check the current DST: **`[Expert@HostName]# /usr/sbin/zdump -v Asia/Jerusalem | grep `** Example for year 2013: > > ``` > [Expert@HostName]# /usr/sbin/zdump -v Asia/Jerusalem | grep 2013 > Asia/Jerusalem Thu Mar 28 23:59:59 2013 UTC = Fri Mar 29 01:59:59 2013 IST isdst=0 gmtoff=7200 > Asia/Jerusalem Fri Mar 29 00:00:00 2013 UTC = Fri Mar 29 03:00:00 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Sep 7 22:59:59 2013 UTC = Sun Sep 8 01:59:59 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Sep 7 23:00:00 2013 UTC = Sun Sep 8 01:00:00 2013 IST isdst=0 gmtoff=7200 > ``` 5. Hardware clock should already be in UTC: **`[Expert@HostName]# hwclock --utc`** 6. Install the hotfix: * Gaia version R75.45 only: **`[Expert@HostName]# cd /some_path_to_fix/`** **`[Expert@HostName]# tar -zxvf SecurePlatform_HOTFIX_FOXX_HF_HA45_091.tgz`** **`[Expert@HostName]# ./SecurePlatform_HOTFIX_FOXX_HF_HA45_091_`*BUILD*** * Gaia all versions (listed above) other than R75.45: **`[Expert@HostName]# cd /some_path_to_fix/`** **`[Expert@HostName]# rpm -Uhv --force --nodeps tzdata-2010i-1.el5.cp986091001.noarch.rpm `**

7. Verify that DST was changed: **`[Expert@HostName]# /usr/sbin/zdump -v Asia/Jerusalem | grep `** Example for year 2013: > > ``` > [Expert@HostName]# /usr/sbin/zdump -v Asia/Jerusalem | grep 2013 > Asia/Jerusalem Thu Mar 28 23:59:59 2013 UTC = Fri Mar 29 01:59:59 2013 IST isdst=0 gmtoff=7200 > Asia/Jerusalem Fri Mar 29 00:00:00 2013 UTC = Fri Mar 29 03:00:00 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Oct 26 22:59:59 2013 UTC = Sun Oct 27 01:59:59 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Oct 26 23:00:00 2013 UTC = Sun Oct 27 01:00:00 2013 IST isdst=0 gmtoff=7200 > ```



* Hotfix for IPSO 6.2 OS {#IPSO} ------------------------------ **Hotfix installation instructions:** 1. Hotfix has to be installed only on IPSO-based machine. 2. Check the current DST: **`hostname[admin]# zdump -v Asia/Jerusalem | grep `** Example for year 2013: > > ``` > hostname[admin]# zdump -v Asia/Jerusalem | grep 2013 > Asia/Jerusalem Thu Mar 28 23:59:59 2013 UTC = Fri Mar 29 01:59:59 2013 IST isdst=0 gmtoff=7200 > Asia/Jerusalem Fri Mar 29 00:00:00 2013 UTC = Fri Mar 29 03:00:00 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Sep 7 22:59:59 2013 UTC = Sun Sep 8 01:59:59 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Sep 7 23:00:00 2013 UTC = Sun Sep 8 01:00:00 2013 IST isdst=0 gmtoff=7200 > ``` 3. Transfer the new timezone file (**`Jerusalem.sk92568`** ) to the machine (e.g., into `/some_path_to_fix/`). 4. Rename the file from **`Jerusalem.sk92568`** to **`Jerusalem`** **`hostname[admin]# cd /some_path_to_fix/`** **`hostname[admin]# mv Jerusalem.sk92568 Jerusalem`** 5. Verify the MD5 of the file: **`hostname[admin]# md5 Jerusalem`** 6. Mount the root partition in read-write: **`hostname[admin]# mount -u /`** 7. Backup the original timezone file: **`hostname[admin]# cp -p /image/current/usr/share/zoneinfo/Asia/Jerusalem{,.orig}`** 8. Replace the original timezone file with the new file: **`hostname[admin]# cp /some_path_to_fix/Jerusalem /image/current/usr/share/zoneinfo/Asia/Jerusalem`** 9. Mount the root partition in read-only: **`hostname[admin]# mount -u -oro /`** 10. Verify that DST was changed: **`hostname[admin]# zdump -v Asia/Jerusalem | grep `** Example for year 2013: > > ``` > hostname[admin]# zdump -v Asia/Jerusalem | grep 2013 > Asia/Jerusalem Thu Mar 28 23:59:59 2013 UTC = Fri Mar 29 01:59:59 2013 IST isdst=0 gmtoff=7200 > Asia/Jerusalem Fri Mar 29 00:00:00 2013 UTC = Fri Mar 29 03:00:00 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Oct 26 22:59:59 2013 UTC = Sun Oct 27 01:59:59 2013 IDT isdst=1 gmtoff=10800 > Asia/Jerusalem Sat Oct 26 23:00:00 2013 UTC = Sun Oct 27 01:00:00 2013 IST isdst=0 gmtoff=7200 > ``` 11. Reboot the machine, so that all the processes will start with the correct timezone. Note: During boot, the `/bin/tz_xlate` writes the `/etc/localtime` file from `/usr/share/zoneinfo`.

**Note:** Updated timezone data can be prepared on any IPSO 6.2 machine. 1. Go to [`http://www.iana.org/time-zones/`](http://www.iana.org/time-zones/). 2. Download latest **`tzdata`** . 3. Transfer the file to the IPSO machine. 4. Create the relevant directory: **`hostname[admin]# mkdir tzdata`** 5. Unpack the `tzdata`: **`hostname[admin]# tar -xf tzdata`*VERSION*`.tar.gz -C tzdata`** 6. Go to the relevant directory: **`hostname[admin]# cd tzdata`** 7. Compile the timezone: **`hostname[admin]# zic -d . asia`** 8. The file for Israel will be in **`Asia/Jerusalem`**. --- # Agent Instructions This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products. ## Navigating This Knowledge Base - **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt) - **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml) - **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}` - **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content