this post was submitted on 05 Jan 2026
333 points (99.4% liked)

PC Gaming

13158 readers
806 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] tgxn@lemmy.tgxn.net 1 points 1 day ago* (last edited 1 day ago) (1 children)

The issue here is this is a client certificate, issued within the League client, for seemingly local<->local traffic. This ain't no typical HTTPS ceritifcate, it's bundled into the client build. See from the source "League client's hard-coded certificate meant someone at Riot would've needed to remember it required updating before its expiration date." So, not quite as easy as configuring an ACME CRON, but something that'd need to be remembered or have some kind of internal reminder for.

[–] AmbiguousProps@lemmy.today 2 points 1 day ago

I'm aware, but it should have been part of their build system and they should have, at the very least, had alarms for this.