Schrödinger's Registration when PC clock is behind Den Clock
so apparently if the PC's clock is behind the Den even by as little as 10 minutes, a registration of a PC goes through without any errors but if you OK out the settings and go back in, you'll find out that the registration has in fact not been properly applied.
the certificate hasnt been valid from the viewpoint of the computer, yes but it maybe should error out appropriately to tell the user that the time may be off. also setting the not before a little before the actual issuance or having some other kind of failsafe will help when DST strikes back in the end of October (where machines literally go back in local time by an hour, where ideally if properly verifing via UTC times nothing should happen, but I have seen a lot in software.)
Wayk now 2020.2.1
Wayk Den Software information
PS Version
7.0.3
Cmdlet Version
2020.2.2
Docker Version
19.03.12
Docker images
Den Server Image
devolutions/den-server:2.6.0-buster
Den Picky Image
devolutions/picky:4.5.0-buster
Den Lucid Image
devolutions/den-lucid:3.7.2-buster
Traefik Image
library/traefik:1.7
Mongo Image
library/mongo:4.2-bionic
Server information
Os Version Info
Linux Ubuntu 20.04 LTS
Den Version
3
All Comments (2)
Hi,
Time validation is done using standard UNIX timestamps (https://en.wikipedia.org/wiki/Unix_time), which is the number of seconds since January 1st, 1970 (Epoch time). This time representation is not affected by time zones (the same timestamp is converted to different times in different time zones when converted to local time, but the timestamp itself doesn't care about time zones). Daylight Saving Time is not at cause here, and won't break Wayk, as it is safe from time zone interference.
What can cause trouble, however, is an incorrect system clock. We did put some effort into supporting systems that have a misconfigured system clock, but there are some cases where it can still break parts of the application. When connecting to Wayk Den, we do a simple time clock difference check (not very precise, but good enough to detect large clock differences) and apply a time fix inside our application on top of the reported system clock. We were wary of fiddling with this, so the time fix is only applied for very large time differences, I believe 10 minutes off would currently remain untouched, but would still be sufficient to break things.
At this point, consider the following:
1) Wayk Den *MUST* have a good clock. We won't ever try doing anything to make it work with a bad clock, there is no point. Just get it correctly synchronized.
2) Wayk Now *SHOULD* have a good clock, but for now, just make sure your clocks are correct. We did put some effort to try and make things work with a bad clock, but we don't officially support bad clocks at this point. In other words, don't expect it to work, so fix your system clock again.
Best regards,
Marc-André Moreau
cool that unixtime is used is very nice. I use it myself in programming all the time since it's very easy to use in PHP and stuff.
In other words, don't expect it to work
My problem was never that it didnt work. but rather that it didnt properly fail, but give the appearance that it worked until a minute or 2 later when you can see in the den that the registration didnt apply
.
like if the time is off, you might wanna tell the user or whatever