this post was submitted on 18 Aug 2023
168 points (97.7% liked)

Technology

60373 readers
8274 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago
MODERATORS
L3s
enu
technopagan
168
Windows feature that resets system clocks based on random data is wreaking havoc (arstechnica.com)
submitted 1 year ago by KelsonV to c/technology
15 comments fedilink hide all child comments
 

STS (Secure Time Seeding) uses server time from SSL handshakes, which is fine when talking to other Microsoft servers, but other implementations put random data in that field to prevent fingerprinting.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

I feel like the 3rd party API should have had some error checking, although that might have strayed too far into a client's business logic.
If it is an API of incidents, that suggests past incidents. And the whole "never trust user data" kinda implies they should throw an error if you request information about a tinerange in the future.
I guess, not throwing an error does allow the 3rd party to "schedule" an incident in the future, eg planned maintenance/downtime.

But then, that isn't separation of concerns. Ideally those endpoint would be separate. One for planned hypothetical incidents and one for historical concrete incidents.

It's definitely an odd scenario where you are taking your trusted data (from your systems and your database), then having to validate it.