why does #google need my tz to match #NTP to check if an expired 2fa #otp is being used?
#2fa
#NTP
Google Time NTP Public Server | https://techygeekshome.info/google-time-ntp-public-server/?fsp_sid=29519 | #Google #Guide #News #NTP #refresh #Servers
https://techygeekshome.info/google-time-ntp-public-server/?fsp_sid=29519
Google Time NTP Public Server | https://techygeekshome.info/google-time-ntp-public-server/?fsp_sid=29518 | #Google #Guide #News #NTP #refresh #Servers
https://techygeekshome.info/google-time-ntp-public-server/?fsp_sid=29518
Almost every system assumes time is correct. Certificates expire, logs align, databases replicate, caches invalidate. Yet time synchronization is treated as background noise.
I would argue that NTP is one of the most critical services on the internet, and almost no one thinks about it unless it breaks. When it does, failures cascade in ways that look unrelated. Authentication fails. Distributed systems disagree. Debugging becomes guesswork.
Time is infrastructure. It just hides better than most.
#Infrastructure #DistributedSystems #NTP #Infosec #TechReality
@silverpill #TLS could be an issue if global #NTP/123 is down; some users may be surprised that they cannot access the Internet using 'old' devices that do not have the ability to upgrade their software from outdated repositories.
Solving all the issues I found one by one in my #homelab after a major internet outage.
Seems like the time sync issue on the #Philips #Hue bridge is ongoing. It pops out here and there periodically, and no general solution has been found.
It's not a big deal until you are using time-based scenes, like me.
So now I'm trying to trick the bridge into using my local #NTP server.
Seems like only 1 IPv4 and 3 IPv6 servers left in BD country NTP pool https://www.ntppool.org/zone/bd
Seems like 2.antarctica.pool.ntp.org is a thing. None of the other [0/1/3].antarctica.pool.ntp.org have any IP as 3 servers in pool (https://www.ntppool.org/zone/aq ) are IPv6 only (https://bgp.tools/dns/2.antarctica.pool.ntp.org).
@karppinen Maybe you could respond to them with a slightly wrong time so the queries will disperse around the next hour instead of a huge spike. #ChaoticEvil #NTP
Introducing Pixie; yet another GNSS disciplined Raspberry Pi timeserver setup. There are a number of low-level tweaks including a realtime kernel build, per-CPU process isolation, PTP grandmaster time support, and NTP server support. Check out the wiki for more details!
https://github.com/josh-blake/pixie #gnss #raspberrypi #rpi5 #embedded #timeserver #ptp #ntp
NTP in practice. Mostly it works. Time to time it's like 8 hours off. Internet connection is working.
I already debugged unreliable NTP once and replaced the unreliable "ntp" NTP daemon with much more reliable "chrony" NTP daemon. But still unreliable.
"Old people don't like computers" - because computers are unreliable! Why would I use something that's unreliable? A tuning fork ground out of quartz, invented by Seiko, connected to a battery, semiconductor amplifier, 15-bit counter, few logic gates, stepper motor, cogwheels, hands and a clock face is much more reliable!
#ntp #unreliable #linuxfail #linux #chrony #ntpd #reliability
Made a quick #substack post about an idea that's been floating around in my brain re: proving the when of digital signatures:
https://open.substack.com/pub/bigntallmike/p/digital-signatures-arent-enough-yet?r=6i7fw3
WIP. Feedback appreciated.
I had to troubleshoot #NTP servers a few times without access to my laptop so I built this app two years ago. Today, I decided to release it for free for anyone who wants to use it. Find the NTP Inspector on the App Store!
TIL: Besides UTC, there also is TAI – Temps Atomics International aka International Atomic Time. And well … TAI currently is UTC +37s 🤯
For other interesting things about time, computer time and time protocols, I highly recommend the talk on PTP from last years #39C3: https://media.ccc.de/v/39c3-excuse-me-what-precise-time-is-it #ptp #ntp #timeprotocol
It spiraled quite hard, as I was also configuring NTP servers between all nodes, which didn't play nice when some node had NTP configured, and others had a big enough drift to not be onboarded... Everything went down, kubernetes service timing out, ingress timing out, everything going down
Nur die Richtigkeit der Zeit bringt die Richtigkeit der Realität. Für eine Annäherung dessen bin ich immer zu haben.
Auf dem #39c3 wurde #PTP zur Synchronisation der Video Aufzeichnungen genutzt. #NTP mit mehreren ms Abweichung ist spürbar. Aber im Q&A Teil zweifel ich an, dass unser Gehör und Gehirn im ns Bereich arbeitet. µs Genauigkeit denke ich hier wäre richtig.
Und ab ins Rabbit Hole und zig Webseiten mit abweichender genauer Richtigkeit.
https://media.ccc.de/v/39c3-excuse-me-what-precise-time-is-it
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst