Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDebian Templates: /etc/timezone being kept reset to UTC #1154
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesuser
Aug 30, 2015
Isn't the proper solution to fix Qubes to optionally not provide the configured timezone to select or all VMs?
Otherwise an exploited Whonix Workstation can access it anyway with qubesdb-read /qubes-timezone, while once that is fixed, setting the correct UTC timezone becomes automatic.
qubesuser
commented
Aug 30, 2015
|
Isn't the proper solution to fix Qubes to optionally not provide the configured timezone to select or all VMs? Otherwise an exploited Whonix Workstation can access it anyway with |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Yes, but this is a separate issue. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 30, 2015
Member
Maybe some other startup service? I see systemd-timesynced.service is
started for example, it claims to have even NTP enabled...
Or something calls timedatectl (->systemd-timedated.service), some
application from /etc/xdg/autostart or so.
BTW I've found something strange - /etc is owned by user:user. Does it
happen only to me?
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Maybe some other startup service? I see systemd-timesynced.service is BTW I've found something strange - /etc is owned by user:user. Does it Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
unman
Aug 30, 2015
Member
@adrelanos
How are you setting the timezone? With dpkg-reconfigure tzdata?
It isnt clear to me when it's being reset for you - after every reboot?
I should say that I don't see this behaviour at all.
|
@adrelanos |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Aug 31, 2015
Member
systemd-timedated.service was already disabled. (sudo timedatectl set-ntp 0)
BTW I've found something strange - /etc is owned by user:user. Does it happen only to me?
My Whonix 11 template's /etc is also owned by user. Very strange. @nrgaway any idea?
How are you setting the timezone? With dpkg-reconfigure tzdata?
Yes, for example. But also when I manually edit some extra "xyz" or so it will be lost after reboot.
It isnt clear to me when it's being reset for you - after every reboot?
After every reboot. Otherwise it's unchanged. Whonix 11 templates. I even tried auditd to no avail.
|
systemd-timedated.service was already disabled. (
My Whonix 11 template's /etc is also owned by user. Very strange. @nrgaway any idea?
Yes, for example. But also when I manually edit some extra "xyz" or so it will be lost after reboot.
After every reboot. Otherwise it's unchanged. Whonix 11 templates. I even tried auditd to no avail. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
unman
Aug 31, 2015
Member
I don't see this behaviour in the debian templates.
Unless others do - best to ask on the ml? - that would suggest that it is a whonix issue.
|
I don't see this behaviour in the debian templates. |
marmarek
added
bug
C: core
C: templates
C: Debian
P: major
labels
Sep 1, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Sep 1, 2015
Member
Just checked on whonix-gw based ProxyVM:
user@host:~$ timedatectl status
Local time: Tue 2015-09-01 22:55:30 UTC
Universal time: Tue 2015-09-01 22:55:30 UTC
RTC time: n/a
Time zone: UTC (UTC, +0000)
NTP enabled: yes
NTP synchronized: no
RTC in local TZ: no
DST active: n/a
So probably that timedatectl set-ntp 0 doesn't work as expected or isn't executed at all.
Anyway this service can be responsible for resetting /etc/timezone (based on /etc/localtime? just guessing)
|
Just checked on whonix-gw based ProxyVM:
So probably that |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Sep 1, 2015
Member
timedatectl set-ntp 1 creates /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service and timedatectl set-ntp 0 deletes it. (sudo service systemd-timesyncd status confirms it's disabled.)
That service is already disabled in my development whonix-gw based ProxyVM.
After sudo dpkg-reconfigure tzdata to something else, which works, both /etc/timezone (reset to UTC) and /etc/localtime (reset to copy of /usr/share/zoneinfo) is reset after reboot.
|
That service is already disabled in my development whonix-gw based ProxyVM. After |
marmarek
added this to the Release 3.1 milestone
Sep 5, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
This issue is exclusive to Qubes-Whonix only, which is very strange. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Sep 9, 2015
Member
Fixed in the development version of Qubes-Whonix.
Even though I am sure I had the qubes-whonix postinst script disabled, it seems to no longer happen since:
Whonix/qubes-whonix@d11e428
|
Fixed in the development version of Qubes-Whonix. |
adrelanos commentedAug 29, 2015
cat /etc/timezone:cat /etc/qubes/protected-files.d/persist:Whenever I set it to
Etc/UTCor something arbitrary, its being reset toUTC. It's not the/usr/lib/qubes/init/qubes-sysinit.shscript. I debugged that. [Checked it honors protected-files.d, yes, commented out the timezone modifying code.]What else could keep setting it to
UTC?Maybe
UTCis good enough for Whonix. Dunno ifEtc/UTCwould make a difference. Anyhow. Finding out why would be important in order to understand things.