June 2026 - tz - lists.iana.org

Time Zone Database
by EL MAAYATI Afaf July 8, 2026

July 8, 2026

Dear Paul, I'm Afaf EL MAAYATI from National Telecommunications Regulatory Agency in Morocco. Actually, in the current version of Time Zone Database (https://www.iana.org/time-zones) for Africa region, and especially for Morocco, it’s mentionned that a program will be running to implement the transition dates. According to this program, the next transition dates (during 2023) are as below : - March 19, 2023 (switching to GMT). - April 30, 2023 (switching back to GMT+1). In fact, we will switch back to GMT+1, advancing 60 minutes, on Sunday, April 23 at 2:00 a.m (not on April 30). Please refer to the official annoncement, published by the Ministry of Digital Transition and Administration Reform: https://www.mmsp.gov.ma/fr/actualites/passage-%C3%A0-l%E2%80%99heure-gmt-%C… So, would you please update the program, in order to consider « April 23 at 2:00 a.m » (for switching back to GMT+1). Thank you in advance for your feedback and for your habitual support. Thank you. Best Regards, Afaf EL MAAYATI National Telecommunications Regulatory Agency Morocco [https://www.anrt.ma/images/ANRT-Signature.jpg] ________________________________ Ce message, son contenu et toutes les pièces jointes sont adressés à l'attention exclusive de leur (s) destinataire (s) et sont strictement confidentiels : ils relèvent de la correspondance privée. Toute publication, utilisation ou diffusion, même partielle, par des personnes autres que les destinataires est interdite et doit être autorisée par l'Agence Nationale de Règlementation des Télécommunications (ANRT, Royaume du Maroc). Si vous recevez ce message par erreur, nous vous prions de le détruire après en avoir informé son expéditeur sans délai. L’ANRT décline toute responsabilité pour toute altération, déformation ou falsification subi par le message et ses pièces jointes au cours de leur transmission. Retrouvez toutes les informations de l’ANRT sur son site Web à l’adresse suivante : http://www.anrt.ma. ________________________________ This message, its content and its attachments are intended for the exclusive use of the named addressee (s) and are strictly confidential. Any copy or other use of this information by persons or entities other than the intended recipient is prohibited and should be authorized by the National Agency of Telecommunications Regulation (ANRT, Morocco). If you have received this communication in error, please delete the material and notify the sender. The ANRT accepts no liability for any alteration, distortion or falsification that may occur during the transmission of this message. All information about ANRT can be found on our website at the following address http://www.anrt.ma. ________________________________ إن هذه الرسالة ومحتواها ومرفقاتها موجهة خصيصا للشخص المرسل إليه وتعتبر سرية وتصنف ضمن خانة المراسلات ذات طبيعة شخصية. ويمنع منعا كليا نشر أو استعمال أو بث، ولو بطريقة جزئية، لهذه الرسالة من طرف أشخاص غير المرسل إليهم ما لم يتم الترخيص بذلك من طرف الوكالة الوطنية لتقنين المواصلات (المملكة المغربية. في حالة ما إذا توصلتم هذه الرسالة عن طريق الخطأ، يرجى منكم العمل على إتلافها فورا بعد إخبار الشخص المرسل إليه بذلك. ولا تتحمل الوكالة الوطنية لتقنين المواصلات أي مسؤولية عن أي تحريف أو تغيير أو تزييف قد يلحق بمحتوى الرسالة أو بمرفقاتها خلال عملية الإرسال. للمزيد من المعلومات، يرجى الاطلاع على الموقع الإلكتروني للوكالة الوطنية لتقنين المواصلات : http://www.anrt.ma.

2 6

Request for consideration of a dedicated time zone identifier for Coyhaique, Aysén Region, Chile
by Victor Alfonso July 7, 2026

July 7, 2026

Dear Time Zone Database Maintainers, I am writing from Coyhaique, the capital city of the Aysén Region in Chile, regarding the recent adoption of UTC−03:00 in our region. Currently, many operating systems, applications, and online services identify our location using the existing "America/Punta_Arenas" time zone. While this provides the correct UTC offset, Coyhaique and the Aysén Region do not appear as a selectable or identifiable location in many systems. This can create confusion for local users, organizations, businesses, and visitors who are attempting to verify or configure the correct local time. I would like to respectfully inquire whether the creation of a dedicated time zone identifier, such as "America/Coyhaique", could be considered for inclusion in the IANA Time Zone Database. I understand that new identifiers are generally created when there are historical differences or the possibility of future divergence in timekeeping rules. However, the Aysén Region now operates under UTC−03:00 and has a distinct regional identity and administrative significance that may justify separate representation within systems that rely on the IANA database. In addition, Coyhaique serves as one of the principal gateways to Chilean Patagonia and is the administrative, commercial, and logistical center of the Aysén Region. Every year, the city receives a significant number of domestic and international visitors who rely on digital systems to coordinate flights, accommodations, tours, transportation, and business activities. The absence of a specific identifier for Coyhaique in many operating systems and platforms may create uncertainty regarding the local time zone, particularly for visitors who are unfamiliar with the relationship between Aysén and the "America/Punta_Arenas" identifier. A dedicated reference to Coyhaique could improve clarity and user experience for travelers, businesses, service providers, and software systems operating within the region. If a new identifier is not currently considered necessary, I would greatly appreciate any clarification regarding the criteria that would need to be met for such consideration in the future. Thank you for your time and for the important work you do in maintaining this essential global resource. Kind regards, Víctor Alfonso Coyhaique, Aysén Región. Chile

6 7

Re: Alberta time zone change is now official
by Aoun Khan July 7, 2026

July 7, 2026

Hello, I was following the discussion regarding Alberta’s planned switch to permanent UTC-6:00. I would like to provide the following update that the Act to switch time zones has indeed officially gone through proclamation as of June 18, 2026. https://www.alberta.ca/proclamations Red Tape Reduction Statutes Amendment Act, 2026 (SA 2026 c12). Sections 3, 5(3) to (8) and 11 proclaimed in force on June 18, 2026. Amends the Daylight Saving Time Act(RSA 2000 cD-5), the Gaming, Liquor and Cannabis Act (RSA 2000 cG-1) and the Natural Gas Marketing Act (RSA 2000 cN-1). Section 9(1), (2)(f), (h) and (j), (4) to (6), (9), (11)(a), (68)(a) and (78)(a), (b) and (e) proclaimed in force on September 1, 2026. Amends the Land Titles Act (RSA 2000 cL-4). It’s possible you may already be aware of this, but I just wanted to let you know as the discussion intrigues me. Sincerely, Aoun Khan

4 3

[PROPOSED] Morocco goes to plain UTC on 2026-09-20
by Paul Eggert July 4, 2026

July 4, 2026

This also affects Western Sahara * NEWS: Mention this. * africa (Morocco): Remove transitions after 2026. (Africa/Casablanca, Africa/El_Aaiun): Switch to +00 on 2026-09-20 at 02:00. --- NEWS | 5 ++ africa | 169 ++++----------------------------------------------------- 2 files changed, 15 insertions(+), 159 deletions(-) diff --git a/NEWS b/NEWS index 07e5fc69..459af904 100644 --- a/NEWS +++ b/NEWS @@ -4,6 +4,7 @@ Unreleased, experimental changes Briefly: Alberta moved to permanent -06 on 2026-06-18. + Morocco moves to permanent +00 on 2026-09-20. More integer overflow bugs have been fixed in zic. Changes to future timestamps @@ -16,6 +17,10 @@ Unreleased, experimental changes 02:00 instead, for the same reason we introduced a similarly temporary hack for British Columbia in 2026b. + Morocco plans to move back to permanent UTC, without daylight + saving time transitions, on 2026-09-20 at 02:00. This also + affects Western Sahara. + Changes to code zic no longer overflows integers when processing outlandish input diff --git a/africa b/africa index ec067bee..3517b84c 100644 --- a/africa +++ b/africa @@ -850,33 +850,12 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # The return to legal GMT time will take place this Sunday, March 19 at 3 a.m. # ... the return to GMT+1 will be made on Sunday April 23, 2023 at 2 a.m. # https://www.mmsp.gov.ma/fr/actualites/passage-à-l%E2%80%99heure-gmt-à-parti… -# -# From Paul Eggert (2023-03-14): -# For now, guess that in the future Morocco will fall back at 03:00 -# the last Sunday before Ramadan, and spring forward at 02:00 the -# first Sunday after one day after Ramadan. To implement this, -# transition dates and times for 2019 through 2087 were determined by -# running the following program under GNU Emacs 28.2. (This algorithm -# also produces the correct transition dates for 2016 through 2018, -# though the times differ due to Morocco's time zone change in 2018.) -# (let ((islamic-year 1440)) -# (require 'cal-islam) -# (while (< islamic-year 1511) -# (let ((a (calendar-islamic-to-absolute (list 9 1 islamic-year))) -# (b (+ 1 (calendar-islamic-to-absolute (list 10 1 islamic-year)))) -# (sunday 0)) -# (while (/= sunday (mod (setq a (1- a)) 7))) -# (while (/= sunday (mod b 7)) -# (setq b (1+ b))) -# (setq a (calendar-gregorian-from-absolute a)) -# (setq b (calendar-gregorian-from-absolute b)) -# (insert -# (format -# (concat "Rule\tMorocco\t%d\tonly\t-\t%s\t%2d\t 3:00\t-1:00\t-\n" -# "Rule\tMorocco\t%d\tonly\t-\t%s\t%2d\t 2:00\t0\t-\n") -# (car (cdr (cdr a))) (calendar-month-name (car a) t) (car (cdr a)) -# (car (cdr (cdr b))) (calendar-month-name (car b) t) (car (cdr b))))) -# (setq islamic-year (+ 1 islamic-year)))) + +# From Paul Eggert (2026-06-25): +# https://www.moroccoworldnews.com/2026/06/325034/confirmed-morocco-to-restor… +# Today the Moroccan government adopted Decree No. 2.26.530, which abrogates +# the 2018 decree that put it at +01 with daylight saving during Ramadan. +# The plan is to go back to +00 without DST on 2026-09-20 at 02:00. # Rule NAME FROM TO - IN ON AT SAVE LETTER/S Rule Morocco 1939 only - Sep 12 0:00 1:00 - @@ -936,143 +915,14 @@ Rule Morocco 2025 only - Feb 23 3:00 -1:00 - Rule Morocco 2025 only - Apr 6 2:00 0 - Rule Morocco 2026 only - Feb 15 3:00 -1:00 - Rule Morocco 2026 only - Mar 22 2:00 0 - -Rule Morocco 2027 only - Feb 7 3:00 -1:00 - -Rule Morocco 2027 only - Mar 14 2:00 0 - -Rule Morocco 2028 only - Jan 23 3:00 -1:00 - -Rule Morocco 2028 only - Mar 5 2:00 0 - -Rule Morocco 2029 only - Jan 14 3:00 -1:00 - -Rule Morocco 2029 only - Feb 18 2:00 0 - -Rule Morocco 2029 only - Dec 30 3:00 -1:00 - -Rule Morocco 2030 only - Feb 10 2:00 0 - -Rule Morocco 2030 only - Dec 22 3:00 -1:00 - -Rule Morocco 2031 only - Jan 26 2:00 0 - -Rule Morocco 2031 only - Dec 14 3:00 -1:00 - -Rule Morocco 2032 only - Jan 18 2:00 0 - -Rule Morocco 2032 only - Nov 28 3:00 -1:00 - -Rule Morocco 2033 only - Jan 9 2:00 0 - -Rule Morocco 2033 only - Nov 20 3:00 -1:00 - -Rule Morocco 2033 only - Dec 25 2:00 0 - -Rule Morocco 2034 only - Nov 5 3:00 -1:00 - -Rule Morocco 2034 only - Dec 17 2:00 0 - -Rule Morocco 2035 only - Oct 28 3:00 -1:00 - -Rule Morocco 2035 only - Dec 9 2:00 0 - -Rule Morocco 2036 only - Oct 19 3:00 -1:00 - -Rule Morocco 2036 only - Nov 23 2:00 0 - -Rule Morocco 2037 only - Oct 4 3:00 -1:00 - -Rule Morocco 2037 only - Nov 15 2:00 0 - -Rule Morocco 2038 only - Sep 26 3:00 -1:00 - -Rule Morocco 2038 only - Oct 31 2:00 0 - -Rule Morocco 2039 only - Sep 18 3:00 -1:00 - -Rule Morocco 2039 only - Oct 23 2:00 0 - -Rule Morocco 2040 only - Sep 2 3:00 -1:00 - -Rule Morocco 2040 only - Oct 14 2:00 0 - -Rule Morocco 2041 only - Aug 25 3:00 -1:00 - -Rule Morocco 2041 only - Sep 29 2:00 0 - -Rule Morocco 2042 only - Aug 10 3:00 -1:00 - -Rule Morocco 2042 only - Sep 21 2:00 0 - -Rule Morocco 2043 only - Aug 2 3:00 -1:00 - -Rule Morocco 2043 only - Sep 13 2:00 0 - -Rule Morocco 2044 only - Jul 24 3:00 -1:00 - -Rule Morocco 2044 only - Aug 28 2:00 0 - -Rule Morocco 2045 only - Jul 9 3:00 -1:00 - -Rule Morocco 2045 only - Aug 20 2:00 0 - -Rule Morocco 2046 only - Jul 1 3:00 -1:00 - -Rule Morocco 2046 only - Aug 5 2:00 0 - -Rule Morocco 2047 only - Jun 23 3:00 -1:00 - -Rule Morocco 2047 only - Jul 28 2:00 0 - -Rule Morocco 2048 only - Jun 7 3:00 -1:00 - -Rule Morocco 2048 only - Jul 19 2:00 0 - -Rule Morocco 2049 only - May 30 3:00 -1:00 - -Rule Morocco 2049 only - Jul 4 2:00 0 - -Rule Morocco 2050 only - May 15 3:00 -1:00 - -Rule Morocco 2050 only - Jun 26 2:00 0 - -Rule Morocco 2051 only - May 7 3:00 -1:00 - -Rule Morocco 2051 only - Jun 18 2:00 0 - -Rule Morocco 2052 only - Apr 28 3:00 -1:00 - -Rule Morocco 2052 only - Jun 2 2:00 0 - -Rule Morocco 2053 only - Apr 13 3:00 -1:00 - -Rule Morocco 2053 only - May 25 2:00 0 - -Rule Morocco 2054 only - Apr 5 3:00 -1:00 - -Rule Morocco 2054 only - May 10 2:00 0 - -Rule Morocco 2055 only - Mar 28 3:00 -1:00 - -Rule Morocco 2055 only - May 2 2:00 0 - -Rule Morocco 2056 only - Mar 12 3:00 -1:00 - -Rule Morocco 2056 only - Apr 23 2:00 0 - -Rule Morocco 2057 only - Mar 4 3:00 -1:00 - -Rule Morocco 2057 only - Apr 8 2:00 0 - -Rule Morocco 2058 only - Feb 17 3:00 -1:00 - -Rule Morocco 2058 only - Mar 31 2:00 0 - -Rule Morocco 2059 only - Feb 9 3:00 -1:00 - -Rule Morocco 2059 only - Mar 23 2:00 0 - -Rule Morocco 2060 only - Feb 1 3:00 -1:00 - -Rule Morocco 2060 only - Mar 7 2:00 0 - -Rule Morocco 2061 only - Jan 16 3:00 -1:00 - -Rule Morocco 2061 only - Feb 27 2:00 0 - -Rule Morocco 2062 only - Jan 8 3:00 -1:00 - -Rule Morocco 2062 only - Feb 12 2:00 0 - -Rule Morocco 2062 only - Dec 31 3:00 -1:00 - -Rule Morocco 2063 only - Feb 4 2:00 0 - -Rule Morocco 2063 only - Dec 16 3:00 -1:00 - -Rule Morocco 2064 only - Jan 27 2:00 0 - -Rule Morocco 2064 only - Dec 7 3:00 -1:00 - -Rule Morocco 2065 only - Jan 11 2:00 0 - -Rule Morocco 2065 only - Nov 22 3:00 -1:00 - -Rule Morocco 2066 only - Jan 3 2:00 0 - -Rule Morocco 2066 only - Nov 14 3:00 -1:00 - -Rule Morocco 2066 only - Dec 26 2:00 0 - -Rule Morocco 2067 only - Nov 6 3:00 -1:00 - -Rule Morocco 2067 only - Dec 11 2:00 0 - -Rule Morocco 2068 only - Oct 21 3:00 -1:00 - -Rule Morocco 2068 only - Dec 2 2:00 0 - -Rule Morocco 2069 only - Oct 13 3:00 -1:00 - -Rule Morocco 2069 only - Nov 17 2:00 0 - -Rule Morocco 2070 only - Oct 5 3:00 -1:00 - -Rule Morocco 2070 only - Nov 9 2:00 0 - -Rule Morocco 2071 only - Sep 20 3:00 -1:00 - -Rule Morocco 2071 only - Nov 1 2:00 0 - -Rule Morocco 2072 only - Sep 11 3:00 -1:00 - -Rule Morocco 2072 only - Oct 16 2:00 0 - -Rule Morocco 2073 only - Aug 27 3:00 -1:00 - -Rule Morocco 2073 only - Oct 8 2:00 0 - -Rule Morocco 2074 only - Aug 19 3:00 -1:00 - -Rule Morocco 2074 only - Sep 30 2:00 0 - -Rule Morocco 2075 only - Aug 11 3:00 -1:00 - -Rule Morocco 2075 only - Sep 15 2:00 0 - -Rule Morocco 2076 only - Jul 26 3:00 -1:00 - -Rule Morocco 2076 only - Sep 6 2:00 0 - -Rule Morocco 2077 only - Jul 18 3:00 -1:00 - -Rule Morocco 2077 only - Aug 22 2:00 0 - -Rule Morocco 2078 only - Jul 10 3:00 -1:00 - -Rule Morocco 2078 only - Aug 14 2:00 0 - -Rule Morocco 2079 only - Jun 25 3:00 -1:00 - -Rule Morocco 2079 only - Aug 6 2:00 0 - -Rule Morocco 2080 only - Jun 16 3:00 -1:00 - -Rule Morocco 2080 only - Jul 21 2:00 0 - -Rule Morocco 2081 only - Jun 1 3:00 -1:00 - -Rule Morocco 2081 only - Jul 13 2:00 0 - -Rule Morocco 2082 only - May 24 3:00 -1:00 - -Rule Morocco 2082 only - Jun 28 2:00 0 - -Rule Morocco 2083 only - May 16 3:00 -1:00 - -Rule Morocco 2083 only - Jun 20 2:00 0 - -Rule Morocco 2084 only - Apr 30 3:00 -1:00 - -Rule Morocco 2084 only - Jun 11 2:00 0 - -Rule Morocco 2085 only - Apr 22 3:00 -1:00 - -Rule Morocco 2085 only - May 27 2:00 0 - -Rule Morocco 2086 only - Apr 14 3:00 -1:00 - -Rule Morocco 2086 only - May 19 2:00 0 - -Rule Morocco 2087 only - Mar 30 3:00 -1:00 - -Rule Morocco 2087 only - May 11 2:00 0 - -# For dates after the somewhat-arbitrary cutoff of 2087, assume that -# Morocco will no longer observe DST. At some point this table will -# need to be extended, though quite possibly Morocco will change the -# rules first. # Zone NAME STDOFF RULES FORMAT [UNTIL] Zone Africa/Casablanca -0:30:20 - LMT 1913 Oct 26 0:00 Morocco %z 1984 Mar 16 1:00 - %z 1986 0:00 Morocco %z 2018 Oct 28 3:00 - 1:00 Morocco %z + 1:00 Morocco %z 2026 Sep 20 2:00 + 0:00 - %z # Western Sahara # @@ -1088,7 +938,8 @@ Zone Africa/Casablanca -0:30:20 - LMT 1913 Oct 26 Zone Africa/El_Aaiun -0:52:48 - LMT 1934 Jan # El Aaiún -1:00 - %z 1976 Apr 14 0:00 Morocco %z 2018 Oct 28 3:00 - 1:00 Morocco %z + 1:00 Morocco %z 2026 Sep 20 2:00 + 0:00 - %z # Botswana # Burundi -- 2.53.0

4 6

B.C. Permanent Daylight Savings
by Matthew Lee July 2, 2026

July 2, 2026

Hello, will this database be updating for B.C. switching permanently to Daylight Savings Time? Thank you.

7 10

[PROPOSED 1/2] tzalloc fails with EFTYPE on invalid TZif files
by Paul Eggert July 1, 2026

July 1, 2026

* localtime.c (tzloadbody): For a TZif file that is not regular or that has a bad format, fail with errno set to EFTYPE, not EINVAL. This fits better with BSD tradition going back to 4.4BSD and Berkeley DB in the early 1990s, and is what NetBSD already does when the file is not a regular file. This changes user-visible behavior only for the value of errno just after tzalloc fails. * private.h (EFTYPE): Default to EINVAL, so that behavior does not change on platforms lacking EFTYPE. --- localtime.c | 30 +++++++++++++++--------------- private.h | 3 +++ 2 files changed, 18 insertions(+), 15 deletions(-) diff --git a/localtime.c b/localtime.c index e3b8bb94..158f0150 100644 --- a/localtime.c +++ b/localtime.c @@ -1025,7 +1025,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, < 0) return errno; if (!S_ISREG(st.st_mode)) - return EINVAL; + return EFTYPE; } fid = OPENAT_TZDIR ? openat(dd, relname, oflags) : open(name, oflags); err = errno; @@ -1049,7 +1049,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, } up = &lsp->u.u; nread = read(fid, up->buf, sizeof up->buf); - err = tzheadsize <= nread ? 0 : nread < 0 ? errno : EINVAL; + err = tzheadsize <= nread ? 0 : nread < 0 ? errno : EFTYPE; } close(fid); if (err) @@ -1077,7 +1077,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, && 0 <= charcnt && charcnt <= TZ_MAX_CHARS && 0 <= ttisstdcnt && ttisstdcnt <= TZ_MAX_TYPES && 0 <= ttisutcnt && ttisutcnt <= TZ_MAX_TYPES)) - return EINVAL; + return EFTYPE; datablock_size = (timecnt * stored /* ats */ + timecnt /* types */ @@ -1087,12 +1087,12 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, + ttisstdcnt /* ttisstds */ + ttisutcnt); /* ttisuts */ if (nread < tzheadsize + datablock_size) - return EINVAL; + return EFTYPE; if (skip_datablock) p += datablock_size; else if (! ((ttisstdcnt == typecnt || ttisstdcnt == 0) && (ttisutcnt == typecnt || ttisutcnt == 0))) - return EINVAL; + return EFTYPE; else { int_fast64_t prevtr = -1; int_fast32_2s prevcorr; @@ -1115,7 +1115,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, ? TIME_T_MIN : at); if (timecnt && attime <= sp->ats[timecnt - 1]) { if (attime < sp->ats[timecnt - 1]) - return EINVAL; + return EFTYPE; sp->types[i - 1] = 0; timecnt--; } @@ -1128,7 +1128,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, for (i = 0; i < sp->timecnt; ++i) { unsigned char typ = *p++; if (sp->typecnt <= typ) - return EINVAL; + return EFTYPE; if (sp->types[i]) sp->types[timecnt++] = typ; } @@ -1142,18 +1142,18 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, cause trouble both in this file and in callers. Also, it violates RFC 9636 section 3.2. */ if (utoff < -TWO_31_MINUS_1) - return EINVAL; + return EFTYPE; ttisp = &sp->ttis[i]; ttisp->tt_utoff = utoff; p += 4; isdst = *p++; if (! (isdst < 2)) - return EINVAL; + return EFTYPE; ttisp->tt_isdst = isdst; desigidx = *p++; if (! (desigidx < sp->charcnt)) - return EINVAL; + return EFTYPE; ttisp->tt_desigidx = desigidx; } for (i = 0; i < sp->charcnt; ++i) @@ -1172,7 +1172,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, /* Leap seconds cannot occur before the Epoch, or out of order. */ if (tr <= prevtr) - return EINVAL; + return EFTYPE; /* To avoid other botches in this code, each leap second's correction must differ from the previous one's by 1 @@ -1184,7 +1184,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, ? corr == prevcorr + 1 : (corr == prevcorr || corr == prevcorr - 1)))) - return EINVAL; + return EFTYPE; prevtr = tr; prevcorr = corr; @@ -1206,7 +1206,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, ttisp->tt_ttisstd = false; else { if (*p != true && *p != false) - return EINVAL; + return EFTYPE; ttisp->tt_ttisstd = *p++; } } @@ -1218,7 +1218,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, ttisp->tt_ttisut = false; else { if (*p != true && *p != false) - return EINVAL; + return EFTYPE; ttisp->tt_ttisut = *p++; } } @@ -1303,7 +1303,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, } } if (sp->typecnt == 0) - return EINVAL; + return EFTYPE; return 0; } diff --git a/private.h b/private.h index 1e6db08c..b0faaeb9 100644 --- a/private.h +++ b/private.h @@ -243,6 +243,9 @@ strnlen (char const *s, size_t maxlen) # define EINVAL ERANGE #endif +#ifndef EFTYPE +# define EFTYPE EINVAL +#endif #ifndef ELOOP # define ELOOP EINVAL #endif -- 2.54.0

2 3

[PROPOSED] Reject ".." in TZ only when privileged
by Paul Eggert July 1, 2026

July 1, 2026

This better matches the behavior of tzcode 2025b and earlier, and is more compatible with what FreeBSD does. * localtime.c (fstatat) [!AT_FDCWD]: New placeholder function. (tzloadbody): Use O_RESOLVE_BENEATH only when privileged. Use similar logic when on platforms lacking O_RESOLVE_BENEATH; this entails moving the stat check to just before the open/openat, in using fstatat when using openat. --- localtime.c | 47 ++++++++++++++++++++++++++++++----------------- 1 file changed, 30 insertions(+), 17 deletions(-) diff --git a/localtime.c b/localtime.c index 0091b81e..e3b8bb94 100644 --- a/localtime.c +++ b/localtime.c @@ -227,7 +227,7 @@ struct timespec { time_t tv_sec; long tv_nsec; }; /* How many seconds to wait before checking the default TZif file again. Negative means no checking. Default to 61 if DETECT_TZ_CHANGES - (as circa 2025 FreeBSD builds its localtime.c with -DDETECT_TZ_CHANGES), + (as circa 2026 FreeBSD builds its localtime.c with -DDETECT_TZ_CHANGES), and to -1 otherwise. */ #ifndef TZ_CHANGE_INTERVAL # ifdef DETECT_TZ_CHANGES @@ -288,10 +288,12 @@ typedef intmax_t timex_t; # endif #endif -/* Placeholders for platforms lacking openat. */ +/* Placeholders for platforms lacking AT_FCWD, openat, and fstatat. */ #ifndef AT_FDCWD # define AT_FDCWD (-1) /* any negative value will do */ static int openat(int dd, char const *path, int oflag) { unreachable (); } +static int fstatat(int dd, char const *path, struct stat *st, int flags) +{ unreachable(); } #endif /* Port to platforms that lack some O_* flags. Unless otherwise @@ -425,8 +427,7 @@ static char const *utc = etc_utc + sizeof "Etc/" - 1; approach of opening "/usr/share/zoneinfo/America/Los_Angeles". Although the OPENAT_TZDIR approach is less efficient, suffers from spurious EMFILE and ENFILE failures, and is no more secure in practice, - it is how bleeding edge FreeBSD did things from August 2025 - through at least September 2025. */ + bleeding edge FreeBSD started doing it this way in August 2025. */ #ifndef OPENAT_TZDIR # define OPENAT_TZDIR 0 #endif @@ -917,6 +918,7 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, int dd = AT_FDCWD; int oflags = (O_RDONLY | O_BINARY | O_CLOEXEC | O_CLOFORK | O_IGNORE_CTTY | O_NOCTTY | O_REGULAR); + bool might_escape = false; int err; struct stat st; st.st_ctime = 0; @@ -943,16 +945,8 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, continue; else if (issetugid()) return ENOTCAPABLE; - else if (!O_REGULAR) { - /* Check for devices, as their mere opening could have - unwanted side effects. Though racy, there is no - portable way to fix the races. This check is needed - only for files not otherwise known to be non-devices. */ - if (stat(name, &st) < 0) - return errno; - if (!S_ISREG(st.st_mode)) - return EINVAL; - } + else + might_escape = true; } if (relname[0] != '/') { @@ -964,8 +958,12 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, for (component = relname; component[0]; component++) if (component[0] == '.' && component[1] == '.' && component[2] == '/' - && (component == relname || component[-1] == '/')) - return ENOTCAPABLE; + && (component == relname || component[-1] == '/')) { + if (issetugid()) + return ENOTCAPABLE; + might_escape = true; + break; + } } if (OPENAT_TZDIR && !SUPPRESS_TZDIR) { @@ -978,7 +976,10 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, | O_BINARY | O_CLOEXEC | O_CLOFORK | O_DIRECTORY)); if (dd < 0) return errno; - oflags |= O_RESOLVE_BENEATH; + if (O_RESOLVE_BENEATH && issetugid()) { + oflags |= O_RESOLVE_BENEATH; + might_escape = false; + } } } @@ -1014,6 +1015,18 @@ tzloadbody(char const *name, struct state *sp, char tzloadflags, #endif } + /* For a platform that lacks O_REGULAR and a file that might + be outside TZDIR, check that it is a regular file, + as merely opening a device could have unwanted side effects. + Though racy, there is no portable way to fix the race. */ + if (!O_REGULAR && might_escape) { + /* (oflags & O_RESOLVE_BENEATH) must be zero here. */ + if ((OPENAT_TZDIR ? fstatat(dd, relname, &st, 0) : stat(name, &st)) + < 0) + return errno; + if (!S_ISREG(st.st_mode)) + return EINVAL; + } fid = OPENAT_TZDIR ? openat(dd, relname, oflags) : open(name, oflags); err = errno; if (0 <= dd) -- 2.54.0

2 2

Re: Morocco's time is inconsistent between the rearguard mode and the vanguard mode
by liuchao (CR) June 29, 2026

June 29, 2026

It only changes FORMAT from +01/+02 to +01/+00, but the rearguard should be +00/+01. And gmtoff is still 7200. After the patch is installed, rearguard mode: [root@ localhost ~]# timedatectl Local time: Mon 2026-06-29 03:40:52 +00 Universal time: Mon 2026-06-29 01:40:52 UTC RTC time: Mon 2026-06-29 01:43:58 Time zone: Africa/Casablanca (+00, +0200) System clock synchronized: no NTP service: active RTC in local TZ: no vanguard mode: [root@localhost ~]# timedatectl Local time: Mon 2026-06-29 02:40:57 +01 Universal time: Mon 2026-06-29 01:40:57 UTC RTC time: Mon 2026-06-29 01:44:02 Time zone: Africa/Casablanca (+01, +0100) System clock synchronized: no NTP service: active RTC in local TZ: no The attached patch fixes the above bug.

3 8

Morocco's time is inconsistent between the rearguard mode and the vanguard mode
by liuchao (CR) June 27, 2026

June 27, 2026

Hello, I found that after commit d0d949d4b36b0f63db3e25dc1b6ae5065a380c55, Morocco's time is inconsistent between the rearguard mode and the vanguard mode. The gmtoff of the rearguard mode in Morocco from October 28, 2018 to September 19, 2026 is 3600 more than that of the vanguard mode. rearguard mode: [root@ localhost ~]# timedatectl Local time: Sat 2026-06-27 06:26:32 +02 Universal time: Sat 2026-06-27 04:26:32 UTC RTC time: Sat 2026-06-27 04:29:34 Time zone: Africa/Casablanca (+02, +0200) System clock synchronized: no NTP service: active RTC in local TZ: no vanguard mode: [root@localhost ~]# timedatectl Local time: Sat 2026-06-27 05:25:48 +01 Universal time: Sat 2026-06-27 04:25:48 UTC RTC time: Sat 2026-06-27 04:28:50 Time zone: Africa/Casablanca (+01, +0100) System clock synchronized: no NTP service: active RTC in local TZ: no In rearguard mode, the time zone is converted once more. On October 28, 2018, the value of gmtoff changed from 3600 to 7200. zdump Africa/Casablanca -V -c 2018,2027 rearguard mode: Africa/Casablanca Sun Mar 25 01:59:59 2018 UT = Sun Mar 25 01:59:59 2018 +00 isdst=0 gmtoff=0 Africa/Casablanca Sun Mar 25 02:00:00 2018 UT = Sun Mar 25 03:00:00 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun May 13 01:59:59 2018 UT = Sun May 13 02:59:59 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun May 13 02:00:00 2018 UT = Sun May 13 02:00:00 2018 +00 isdst=0 gmtoff=0 Africa/Casablanca Sun Jun 17 01:59:59 2018 UT = Sun Jun 17 01:59:59 2018 +00 isdst=0 gmtoff=0 Africa/Casablanca Sun Jun 17 02:00:00 2018 UT = Sun Jun 17 03:00:00 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun Oct 28 01:59:59 2018 UT = Sun Oct 28 02:59:59 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun Oct 28 02:00:00 2018 UT = Sun Oct 28 04:00:00 2018 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun May 5 00:59:59 2019 UT = Sun May 5 02:59:59 2019 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun May 5 01:00:00 2019 UT = Sun May 5 02:00:00 2019 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Jun 9 00:59:59 2019 UT = Sun Jun 9 01:59:59 2019 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Jun 9 01:00:00 2019 UT = Sun Jun 9 03:00:00 2019 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Apr 19 00:59:59 2020 UT = Sun Apr 19 02:59:59 2020 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Apr 19 01:00:00 2020 UT = Sun Apr 19 02:00:00 2020 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun May 31 00:59:59 2020 UT = Sun May 31 01:59:59 2020 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun May 31 01:00:00 2020 UT = Sun May 31 03:00:00 2020 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Apr 11 00:59:59 2021 UT = Sun Apr 11 02:59:59 2021 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Apr 11 01:00:00 2021 UT = Sun Apr 11 02:00:00 2021 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun May 16 00:59:59 2021 UT = Sun May 16 01:59:59 2021 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun May 16 01:00:00 2021 UT = Sun May 16 03:00:00 2021 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Mar 27 00:59:59 2022 UT = Sun Mar 27 02:59:59 2022 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Mar 27 01:00:00 2022 UT = Sun Mar 27 02:00:00 2022 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun May 8 00:59:59 2022 UT = Sun May 8 01:59:59 2022 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun May 8 01:00:00 2022 UT = Sun May 8 03:00:00 2022 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Mar 19 00:59:59 2023 UT = Sun Mar 19 02:59:59 2023 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Mar 19 01:00:00 2023 UT = Sun Mar 19 02:00:00 2023 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 23 00:59:59 2023 UT = Sun Apr 23 01:59:59 2023 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 23 01:00:00 2023 UT = Sun Apr 23 03:00:00 2023 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Mar 10 00:59:59 2024 UT = Sun Mar 10 02:59:59 2024 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Mar 10 01:00:00 2024 UT = Sun Mar 10 02:00:00 2024 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 14 00:59:59 2024 UT = Sun Apr 14 01:59:59 2024 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 14 01:00:00 2024 UT = Sun Apr 14 03:00:00 2024 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Feb 23 00:59:59 2025 UT = Sun Feb 23 02:59:59 2025 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Feb 23 01:00:00 2025 UT = Sun Feb 23 02:00:00 2025 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 6 00:59:59 2025 UT = Sun Apr 6 01:59:59 2025 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 6 01:00:00 2025 UT = Sun Apr 6 03:00:00 2025 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Feb 15 00:59:59 2026 UT = Sun Feb 15 02:59:59 2026 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Feb 15 01:00:00 2026 UT = Sun Feb 15 02:00:00 2026 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Mar 22 00:59:59 2026 UT = Sun Mar 22 01:59:59 2026 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Mar 22 01:00:00 2026 UT = Sun Mar 22 03:00:00 2026 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sat Sep 19 23:59:59 2026 UT = Sun Sep 20 01:59:59 2026 +02 isdst=1 gmtoff=7200 Africa/Casablanca Sun Sep 20 00:00:00 2026 UT = Sun Sep 20 00:00:00 2026 +00 isdst=0 gmtoff=0 vanguard mode: Africa/Casablanca Sun Mar 25 01:59:59 2018 UT = Sun Mar 25 01:59:59 2018 +00 isdst=0 gmtoff=0 Africa/Casablanca Sun Mar 25 02:00:00 2018 UT = Sun Mar 25 03:00:00 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun May 13 01:59:59 2018 UT = Sun May 13 02:59:59 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun May 13 02:00:00 2018 UT = Sun May 13 02:00:00 2018 +00 isdst=0 gmtoff=0 Africa/Casablanca Sun Jun 17 01:59:59 2018 UT = Sun Jun 17 01:59:59 2018 +00 isdst=0 gmtoff=0 Africa/Casablanca Sun Jun 17 02:00:00 2018 UT = Sun Jun 17 03:00:00 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun Oct 28 01:59:59 2018 UT = Sun Oct 28 02:59:59 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun Oct 28 02:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun May 5 01:59:59 2019 UT = Sun May 5 02:59:59 2019 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun May 5 02:00:00 2019 UT = Sun May 5 02:00:00 2019 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Jun 9 01:59:59 2019 UT = Sun Jun 9 01:59:59 2019 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Jun 9 02:00:00 2019 UT = Sun Jun 9 03:00:00 2019 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 19 01:59:59 2020 UT = Sun Apr 19 02:59:59 2020 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 19 02:00:00 2020 UT = Sun Apr 19 02:00:00 2020 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun May 31 01:59:59 2020 UT = Sun May 31 01:59:59 2020 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun May 31 02:00:00 2020 UT = Sun May 31 03:00:00 2020 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 11 01:59:59 2021 UT = Sun Apr 11 02:59:59 2021 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Apr 11 02:00:00 2021 UT = Sun Apr 11 02:00:00 2021 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun May 16 01:59:59 2021 UT = Sun May 16 01:59:59 2021 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun May 16 02:00:00 2021 UT = Sun May 16 03:00:00 2021 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Mar 27 01:59:59 2022 UT = Sun Mar 27 02:59:59 2022 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Mar 27 02:00:00 2022 UT = Sun Mar 27 02:00:00 2022 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun May 8 01:59:59 2022 UT = Sun May 8 01:59:59 2022 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun May 8 02:00:00 2022 UT = Sun May 8 03:00:00 2022 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Mar 19 01:59:59 2023 UT = Sun Mar 19 02:59:59 2023 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Mar 19 02:00:00 2023 UT = Sun Mar 19 02:00:00 2023 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Apr 23 01:59:59 2023 UT = Sun Apr 23 01:59:59 2023 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Apr 23 02:00:00 2023 UT = Sun Apr 23 03:00:00 2023 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Mar 10 01:59:59 2024 UT = Sun Mar 10 02:59:59 2024 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Mar 10 02:00:00 2024 UT = Sun Mar 10 02:00:00 2024 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Apr 14 01:59:59 2024 UT = Sun Apr 14 01:59:59 2024 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Apr 14 02:00:00 2024 UT = Sun Apr 14 03:00:00 2024 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Feb 23 01:59:59 2025 UT = Sun Feb 23 02:59:59 2025 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Feb 23 02:00:00 2025 UT = Sun Feb 23 02:00:00 2025 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Apr 6 01:59:59 2025 UT = Sun Apr 6 01:59:59 2025 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Apr 6 02:00:00 2025 UT = Sun Apr 6 03:00:00 2025 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Feb 15 01:59:59 2026 UT = Sun Feb 15 02:59:59 2026 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Feb 15 02:00:00 2026 UT = Sun Feb 15 02:00:00 2026 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Mar 22 01:59:59 2026 UT = Sun Mar 22 01:59:59 2026 +00 isdst=1 gmtoff=0 Africa/Casablanca Sun Mar 22 02:00:00 2026 UT = Sun Mar 22 03:00:00 2026 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Sep 20 00:59:59 2026 UT = Sun Sep 20 01:59:59 2026 +01 isdst=0 gmtoff=3600 Africa/Casablanca Sun Sep 20 01:00:00 2026 UT = Sun Sep 20 01:00:00 2026 +00 isdst=0 gmtoff=0

2 1

[PROPOSED] Comment on pre-2008 Morocco data unreliability
by Paul Eggert June 26, 2026

June 26, 2026

* africa: Add a comment citing Latifa Babas’s March piece that persuasively disagrees with our pre-2008 Morocco data. Perhaps someone with more expertise in navigating sgg.gov.ma can dig out the original decrees and fix our data. --- africa | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/africa b/africa index 3517b84c..271bf87e 100644 --- a/africa +++ b/africa @@ -597,6 +597,24 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # Morocco # See Africa/Ceuta for Spanish Morocco. +# From Paul Eggert (2026-06-26): +# In “Morocco’s GMT+1, a century of shifting time and a debate far from over” +# https://en.yabiladi.com/articles/details/191310/morocco-s-gmt1-century-shif… +# (2026-03-30), Yabiladi’s Latifa Babas reports the following: +# * A 1913-10-26 royal dahir established GMT as legal time in Morocco. +# * A 1918-05-10 dahir instituted DST on 1918-05-16 at 00:00. +# * A September 1939 dahir restarted DST on 1939-09-12. +# * A February 1940 dahir restarted DST as early as 1940-02-25. +# * Standard time resumed in September 1946. +# * A June 1950 decree restarted DST, which ran until as late as October. +# * Royal decree 455-67 (1967-06-02) restarted DST on June 3 at noon. +# * After 1967 Morocco used DST “during several summers, particularly +# throughout the 1970s and 1980s.” +# Babas consulted official records that disagree with and are surely +# more correct than our pre-2008 timestamp data, which came from the +# unreliable Shanks & Pottenger. Unfortunately, Babas did not provide +# enough detail to correct our data. + # From Alex Krivenyshev (2008-05-09): # Here is an article that Morocco plan to introduce Daylight Saving Time between # 1 June, 2008 and 27 September, 2008. -- 2.53.0

1 0