[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Slapd strftime(3) ISO-8601 patch
> If you are using this timestamp in the CreateTimeStamp or
> ModifyTimeStamp attributes, I believe this change violates the LDAP
> standard. RFC2252 refers to the ASN.1 standards for the definition of
> GeneralizedTime and UTCTime. ASN.1 refers to ISO-8601, but explicitly
> disallows the use of separators.
>
> Moreover, RFC2252 requires the specification of a time zone, and
> "strongly recommends" that GMT time be used.
>
> So, if you choose to use this patch, be aware that conforming clients
> may not behave correctly.
Damn. Ok, remove the separators from the format string macros. Since
the timezone is required and most versions of strftime(3) won't generate
offsets, it looks like we're stuck with the ugly form of UTC. (Or at
least those of us who have to worry about Daylight Savings Time. Others
could add a constant offset to the localtime version of the format string.)
Remove the separators from the format string macros. The rest of the
patch should still stand.
-Pat