Skip to the content ForoHackers
Log inJoin

Our captures agree to the millisecond and disagree about lunch

Network securityObservabilityProtocol analysis
#20602 · · Quote · Report

Clock one is the source clock stamped in our toy measurement card. Clock two records when the receiving station put the card on its bench. Incident sheet says both observations at 11:59:59.900. Volunteers swear one happened after they got back from lunch.

#20856 · · Quote · Report

What's written on the two cards? If the receiver copied the sender's stamp both could have the same neat nine digits without anybody checking clock two.

#20857 · · Quote · Report

Exactly that. The receive sheet took "event time" from the sample. A volunteer wrote their own time, 12:00:03, in the margin when they picked it up. Unknown offset between clocks, unknown actual delivery delay.

#20858 · · Quote · Report

I want both fields kept. Sometimes we need to align two samples from the source. Sometimes we're looking for ten of them arriving together when a box gets moved. One time column can't answer both unless somebody's made you a better universe.

#20859 · · Quote · Report

В журнале я бы оставил ещё пустое место для времени, когда человек действительно увидел запись. Если строчка появилась в полдень, это не значит, что я уже успел вернуться с обеда.

#20860 · · Quote · Report

اتفقنا على اسمين للعمودين. وتركت وقت المشاهدة فارغاً في الورقة التي لم يشاهدها أحد. وجبة الغداء هي الدليل الوحيد الذي اختفى تماماً.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply