Skip to content

Comment on Broken VPNs, the Year 2038, and certs that expired 100 years ago

Comments

Not nearly as interesting a story: in 1996 I visited a customer who was using up for dialup services, but reported some of their Windows desktops couldn't connect.

It didn't take me long to figure out that the computers that weren't working had their clocks set well into the 21st century. The shell couldn't even display the year properly, I assumed a Y2K incompatibility, but after so many years now I can't remember exactly what I saw.

Anyway, easy fix, but I never did find out what caused such a weird glitch in their environment. It's small wonder that many people aren't fluent with computers: they misbehave in such a wide variety of ways.

Last year I had a (of many) freshly provisioned Linux VMs clock change to the year 2257 2 nights in a row. Never figured that out sadly, reprovisioning "fixed" that.

Ambassador Kosh's ship arrives at the Epsilon III Jumpgate two days ahead of schedule. Upon leaving his ship the Minbari assassin approaches Kosh in the guise of Jeffrey Sinclair, whom Kosh recognises as Entil'Zha Valen. When he extends a hand in greeting to his 'old friend' the Minbari slaps a skin tab dosed with Florazyne, causing Kosh to collapse and lose consciousness

Oh no.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.