From: Rich Felker <dalias@libc.org>
To: "Sören Tempel" <soeren@soeren-tempel.net>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Handling of non-location specific TZ values
Date: Sat, 5 Jun 2021 11:52:13 -0400 [thread overview]
Message-ID: <20210605155213.GG13220@brightrain.aerifal.cx> (raw)
In-Reply-To: <3MGPR9AUMAQHJ.2LO2SEGZT22CO@8pit.net>
On Wed, Jun 02, 2021 at 05:41:30PM +0200, Sören Tempel wrote:
> Ping.
>
> Would be willing to adjust the patch as needed. In any case, it would be
> nice to get this fixed as it currently causes some test failures of
> Alpine packages.
Thanks for the ping. I had an alternate approach in draft that I want
to look back at and compare. I'll try to get this fixed one way or the
other before rolling the release.
Rich
> Sören Tempel <soeren@soeren-tempel.net> wrote:
> > Rich Felker <dalias@libc.org> wrote:
> > > Yes. I suspect we can get by with calling getname with a dummy output
> > > array, then checking if the next character is one of +, -, or a digit.
> > > If not (in particular, if it's a null character) then we can attempt
> > > loading it as a file.
> >
> > Maybe something along the following? Not too familiar with the musl code
> > base so not sure if including ctype.h is allowed etc.
> >
> > diff --git a/src/time/__tz.c b/src/time/__tz.c
> > index 09a6317e..6bc183d0 100644
> > --- a/src/time/__tz.c
> > +++ b/src/time/__tz.c
> > @@ -3,6 +3,7 @@
> > #include <limits.h>
> > #include <stdlib.h>
> > #include <string.h>
> > +#include <ctype.h>
> > #include <sys/mman.h>
> > #include "libc.h"
> > #include "lock.h"
> > @@ -125,13 +126,13 @@ static size_t zi_dotprod(const unsigned char *z, const unsigned char *v, size_t
> > static void do_tzset()
> > {
> > char buf[NAME_MAX+25], *pathname=buf+24;
> > - const char *try, *s, *p;
> > + const char *try, *s, *orig;
> > const unsigned char *map = 0;
> > size_t i;
> > static const char search[] =
> > "/usr/share/zoneinfo/\0/share/zoneinfo/\0/etc/zoneinfo/\0";
> >
> > - s = getenv("TZ");
> > + s = orig = getenv("TZ");
> > if (!s) s = "/etc/localtime";
> > if (!*s) s = __utc;
> >
> > @@ -154,11 +155,19 @@ static void do_tzset()
> > }
> > if (old_tz) memcpy(old_tz, s, i+1);
> >
> > - /* Non-suid can use an absolute tzfile pathname or a relative
> > - * pathame beginning with "."; in secure mode, only the
> > - * standard path will be searched. */
> > - if (*s == ':' || ((p=strchr(s, '/')) && !memchr(s, ',', p-s))) {
> > + /* The TZ format specified by POSIX consists of a mandatory
> > + * time zone name and a mandatory offset. We determine the
> > + * name using getname, if the next character cannot constitute
> > + * a valid offset (or the TZ value starts with a colon) we
> > + * interpret the TZ environment variable as a zoneinfo file name. */
> > + getname(std_name, &s);
> > + if (*s == ':' || (!isdigit(*s) && *s != '+' && *s != '-')) {
> > if (*s == ':') s++;
> > + else if (orig) s = orig;
> > +
> > + /* Non-suid can use an absolute tzfile pathname or a relative
> > + * pathame beginning with "."; in secure mode, only the
> > + * standard path will be searched. */
> > if (*s == '/' || *s == '.') {
> > if (!libc.secure || !strcmp(s, "/etc/localtime"))
> > map = __map_file(s, &map_size);
> >
> > Patch can be tested using date(1). For instance, compare the output of
> > `TZ=CET date` on a patched and unpatched system with an installed
> > zoneinfo database.
> >
> > > It might be worth adding a special exception for "UTC" and "GMT" so
> > > that they are always interpreted as "UTC0" and "GMT0" and can't be
> > > overridden by a bogus file in the zoneinfo path, for the sake of
> > > software that does "TZ=UTC cmd" to avoid any timezone shenanigans.
> >
> > Maybe that can be done in a separate commit?
> >
> > Greetings,
> > Sören
prev parent reply other threads:[~2021-06-05 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 17:46 Sören Tempel
2021-04-25 18:38 ` Rich Felker
2021-05-02 20:28 ` Sören Tempel
2021-06-02 15:41 ` Sören Tempel
2021-06-05 15:52 ` Rich Felker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210605155213.GG13220@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=soeren@soeren-tempel.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).