Your message dated Fri, 15 Apr 2016 16:52:23 +0000
with message-id <[email protected]>
and subject line Bug#819019: fixed in fake-hwclock 0.11
has caused the Debian Bug report #819019,
regarding fake-hwclock: allow the saved time to go backwards under normal use
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
819019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819019
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fake-hwclock
Version: 0.10
On bug #763589, protection was added around the save operation so that the
saved time cannot go backwards without forcing. While this clearly
mitigates the race condition of concern, I don't believe it is an
acceptable solution for normal users.
Consider the following use case...
1. The user accidentally sets a wrong time to a date in the future -- for
example, sets the year to 2017 rather than 2016
2. The fake-hwclock.data file is written with the future time
3. The user then realizes the mistake, and tries to fix the time back to
the year 2016
4. Now, the cron job and service will not update the fake-hwclock.data,
since it appears that the current system time is in the past (relative to
the invalid saved time)
5. On reboot, the clock reverts to the future date in the year 2017, and
continues to do so on every reboot for the next year (unless the user is
advanced enough to know to manually run the script with the force flag)
Other than races on startup, the normal case is that the system time will
not go backwards unless it was intentionally changed (either by a user or
by an update from an NTP server), so I don't believe it makes sense to
reject such saves by default. (The protection for loads, on the other
hand, is clearly needed.)
For my specific use case, I simply reverted to the original behavior
without any protection against saving, but I suppose the upstream solution
would require an alternate solution to the race reported on #763589.
--
............................................................................
*Roddy Shuler* | +1.585.530.7960 | Endless
--- End Message ---
--- Begin Message ---
Source: fake-hwclock
Source-Version: 0.11
We believe that the bug you reported is fixed in the latest version of
fake-hwclock, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve McIntyre <[email protected]> (supplier of updated fake-hwclock package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 15 Apr 2016 12:32:30 +0100
Source: fake-hwclock
Binary: fake-hwclock
Architecture: source all
Version: 0.11
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <[email protected]>
Changed-By: Steve McIntyre <[email protected]>
Description:
fake-hwclock - Save/restore system clock on machines without working RTC
hardwar
Closes: 819019
Changes:
fake-hwclock (0.11) unstable; urgency=medium
.
* Change the sanity checking behaviour on save. Rather than disallowing
saving a clock prior to the last saved state, now compare to a fixed
date which corresponds to the release of fake-hwclock itself.
Closes: #819019
Checksums-Sha1:
4534d29901be7138b91532a9ec5707cdaa1bc735 1533 fake-hwclock_0.11.dsc
0c2ce3e1ad2c17343f3db25ce05c5f79896490e9 12370 fake-hwclock_0.11.tar.gz
9248f1060d1e77b638041c251fadd30f54d82883 7020 fake-hwclock_0.11_all.deb
Checksums-Sha256:
0a50467ce88b625157f87454a81468abe69c59ffe70138805268e879a6074d3f 1533
fake-hwclock_0.11.dsc
58e29ff272a8e8b40ab972c49f82fd8fb6ef69a7fdde5f84292f800b53ea29ce 12370
fake-hwclock_0.11.tar.gz
0e0c1403f51c21597fac35dab3fd95cbed3b14834872937835da7c82e4517dec 7020
fake-hwclock_0.11_all.deb
Files:
ab532bd39b0c9351fe764a1cd3bd90f2 1533 admin extra fake-hwclock_0.11.dsc
750a6a13557450a03a074c3b23756a94 12370 admin extra fake-hwclock_0.11.tar.gz
93717e0f81daa364964f5204a3880dd8 7020 admin extra fake-hwclock_0.11_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJXEQFjAAoJEFh5eVc0QmhOxHgP/3vRXX/j/a0aGaHjuzTR8Yf9
vwTVFERUSUnCk25AGNDoZc1chd8PuRy6S8UnnxA7zwKtQAuEJ5xlEIUhjYxc7Hcs
d/LPvQxxlwOnPKC8ufY0RHLNfVfdeL2h4FMdSBlS85JfiUtegqGEjJrUB8bpvVq4
IWGQGyTc+x1zx3b6O418eWVn8EGOQ2x3sqNGLesbqv1ATx4WOmWVA+q9vgfFUFDA
7HWi0wD3RYOb6+mE/ttPZOwSNhfbvufRkZjgpOfHbI4ULOP4S7+BA47GwKB9IQGN
s7nWPDzhWlFcdpmd1DvbXTNUmel5BCW96tGQZdx4TnndaEYl6DQ+qf1TDcSKbWgM
AjV0c8jIo3DPnjnbOU6fdXdv4qt+riT56VDdx43LHYZ3QlfHwC0LM4do1NlGziSB
BMihZjTf8gXdx98HJcRXb9iIwf9O70kx8wvJdL4ID+6+kDl7k8CV91qaED9o6u1G
fW8+pj8ZGcm2TqT2x6l2PHMNdyjJCCXoHhcf4f3KeRUdVqZZwGb+1Kqr0Nab5xRd
ljsZK6PbbzcKaww9O4kSQb9slsdo+47/Oh7I96qXdRGtw9fOr2RW8zSxELD2mvgz
jcXiydP5ner6zIqdN2Jxp2sS2RK4KAGCzOoiG6yexbHKC6LZE3uZQYdQ5eLKWl3O
uKovpenaIOgQK+zZhtJv
=5sKI
-----END PGP SIGNATURE-----
--- End Message ---
