!! qubes sudo clock is not returning real clock

28 views
Skip to first unread message

qube...@tutanota.com

unread,
Jul 25, 2018, 1:14:30 PM7/25/18
to Qubes Users
It looks like Qubes is not setting a real clock. Tested over 2 independent connections.

#Real time is "2018-07-25 19:00:00"
#In dom0:
$ sudo clock
2018-07-25 19:03:54.552943+1:00

#My Qubes is continuously getting about 3-4 minutes ahead of a real time.

OATHTOOL
#oathtool --totp needs a real time. If I execute following command I get error
$ oathtool --base32 --totp "my code"

#if I execute following command, setting up the --now "TIME" to the current time manually
#all is working well
$ oathtool --base32 --totp --now "2018-07-25 18:56:00" "my code"

WHONIX
#everytime I switch on the sys-whonix I get a warning the clock is not correct

Is this a known bug, or just my personal issue? How can I solve this issue?
Thank you

Sven Semmler

unread,
Jul 25, 2018, 3:52:58 PM7/25/18
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/25/2018 12:14 PM, qube...@tutanota.com wrote:
> Is this a known bug, or just my personal issue? How can I solve
> this issue?

I have this too. Got it to go away be re-installing the whonix
template but after some updates it came back. No idea what causes it.

/Sven
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAltY1ZcACgkQ2m4We49U
H7YKuxAAt8pgEA9NqI+EDU6/zWWk2P9oryvjmYTAQ8JRoutFOkY/T1WLMfbP1OxY
DIkgbURANXExgVlXXMtsnL2UiVNmtHOOjhcQDTQUyhHtkp9Cseld/8ijBKmLZrfi
bWX+amx9ume0EmhRhPt0QZwz3eQ8p+L2mxDD+O9aLOYBQQdhVT4IoRJRaPFKzBRy
JQNmKwpAN64+ON8ooNVzEbuAqjXX3VvxEd/54JbbQ+uSD1YNERkoAXQXr7JQGRkl
DaS+H2AzLJYfWuMvdpjlGydra98HE0dyX+it0hWYz6So/PZjLQF3ukv9d1UldDtL
Qn4jtwrBYNORkU94kr+KvLIi41Wf98zY24Uov4lrVaRC9/kcV9kjoJqQSDkHKfLJ
xA1W/K7/B40ei7rhmLTd5TLIQHAHtdPW8iq5N/OE87JDTON2P9Hu3I6CKwIEINfs
V3+UVmFhmlvi27zCVFniZW6uagXnol5w7EZ8Xsv9VfOGhteVFVI6VTiADATlLnTI
dZ6Sp9tISht3oDNyidEKiUMS6L4a5cTJfL7YR6YfngnKon7rByOfBj5lWyeChZcl
O8LBVT1dAeehjaRWbIYqEYp5c+YTjx23joaKHxIj1GhniOBDRoP4C/18IgAroNZU
aQETofdn2AVwaCIObCps2HNd0Q1I2uTp6V2GBnXUQ7an8P1tN6o=
=TqA7
-----END PGP SIGNATURE-----

John S.Recdep

unread,
Jul 25, 2018, 7:47:43 PM7/25/18
to qubes...@googlegroups.com
On 07/25/2018 07:14 AM,
I've had it on two different installations, it mysteriously fixes itself
after I blunder around trying to break things. And then tends to stay away.

I believe the Whonix time error is unrelated, as my taskbar dom0 and my
sys-net time are correct, and my UEFI is UTI but I still get the Whonix
errors I'm using version 14

Whonix 13 and 14 both randomly complain, I'm told to "just ignore it"
and that it shouldn't effect Tor security despite the scary message(let
me know if you find out otherwise, I'd like to know)


https://forums.whonix.org/t/qubes-r4-0-rc4-system-time-errors/4844/7
https://forums.whonix.org/t/sys-whonix-14-after-suspend-no-longer-has-a-circuit/5455/3

maybe be sure to run swdate-gui on your sys-whonix ?
Reply all
Reply to author
Forward
0 new messages