Ingo Schwarze wrote:
> Hm, you have a point.
>
> I guess i got confused by my experience with LC_CTYPE; even though
> that is also a standard variable, its effects on different programs
> vary wildly, so the text for LC_CTYPE reads very differently in
> different utility manual pages, and it is o
Hi Theo,
Theo de Raadt wrote on Sat, Jan 05, 2019 at 09:23:46PM -0700:
> Oh good grief, don't do that.
>
> Unless you are going to add the same text to every man page in usr.sbin
> on the following list.
>
> ac bgpd dhcpd httpd ldapd mrouted npppctl nsd ntpd radiusd rdate relayd
> slaacctl smtp
Ted Unangst wrote:
> Ingo Schwarze wrote:
> > Congrats, you found a documentation bug.
> >
> > Apparently, the rdate(8) program supports the TZ environment variable,
> > but the manual page does not say so. An ENVIRONMENT section is missing
> > and should be added. It is not a good idea to giv
Ingo Schwarze wrote:
> >> Demonstrate printing a time modified by TZ instead.
>
> Congrats, you found a documentation bug.
>
> Apparently, the rdate(8) program supports the TZ environment variable,
> but the manual page does not say so. An ENVIRONMENT section is missing
> and should be added.
Ingo Schwarze wrote:
> Congrats, you found a documentation bug.
>
> Apparently, the rdate(8) program supports the TZ environment variable,
> but the manual page does not say so. An ENVIRONMENT section is missing
> and should be added. It is not a good idea to give EXAMPLES for stuff
> that is ac
Theo de Raadt wrote:
> First off, what a weird example you found.
>
> But more on the matter. Is your change even good advice? pool.ntp.org
> is attackable via unauthenticated DNS, and based upon past experience
> who can say if their administrators can even keep their infrastructure
> secure.
Hi Ted,
Theo de Raadt wrote on Sat, Jan 05, 2019 at 08:31:27PM -0700:
> Ted Unangst wrote:
>> The sample server doesn't work for me,
The sample server does work for me:
$ host ptbtime1.ptb.de
ptbtime1.ptb.de has address 192.53.103.108
$ env TZ=UTC rdate -p ptbtime1.ptb.de
Sun Jan 6
First off, what a weird example you found.
But more on the matter. Is your change even good advice? pool.ntp.org
is attackable via unauthenticated DNS, and based upon past experience
who can say if their administrators can even keep their infrastructure
secure. Furthermore, the ntp protocol has
The sample server doesn't work for me, and while the example is a fun hint at
the alternate universe of "right" and "legal" times, I don't think this is a
good place to suggest actually changing the system timezone.
Demonstrate printing a time modified by TZ instead.
Index: rdate.8
=
