linux-kernel - Re: [PATCH 1/6] UML - Deal with host time going backwards

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <303013682@web.de>
Date:	Tue, 03 Jun 2008 21:59:13 +0200
From:	devzero@....de
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	User-mode-linux-devel@...ts.sourceforge.net,
	Jeff Dike <jdike@...toit.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/6] UML - Deal with host time going backwards

>> Protection against the host's time going backwards - keep track of the
>> time at the last tick and if it's greater than the current time, keep
>> time stopped until the host catches up.
>
>Strange.  What would cause the host's time (or at least UML's perception
>of it) to go backwards?

mhh - what about admin`s/user`s stupidity ?

e.g.

0 * * * *   root  /usr/sbin/ntpdate some.time.server >/dev/null 2>&1

in root`s crontab.

if the hosts`s clock is running faster than clock on some.time.server, this would set host`s clock back in time every hour or so....

common malpractice regarding time-syncronization - have seen that more than once.
(and have to admit that i used that some years ago before i wasn`t aware that ntpd does handle that more intelligent)

_______________________________________________________________________
EINE FÜR ALLE: die kostenlose WEB.DE-Plattform für Freunde und Deine
Homepage mit eigenem Namen. Jetzt starten! http://unddu.de/?kid=kid@mf2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/