Riot Games's League of Legends login issues due to expired SSL certificate
old.reddit.com5 pointsby dossy1 comments
> Last refreshed: 2024-01-26 21:04:32Z (UTC)
>
> Current status: Our failover operation did not provide the anticipated relief to end users in North and South America regions and we are now working to optimize traffic patterns as part of the mitigation effort. We’re applying configuration changes across the affected network infrastructure to reduce user impact as quickly as possible.
>
> Next update by: Friday, January 26, 2024, at 11:00 PM UTC INSERT INTO t1 (b,a) values (DEFAULT, 3);
At the time `b` is being evaluated, `a` is to the right of it, so the current value of `a` is its own default value, which is `1`. So, `a+1` will evaluate to `1+1` or `2`. CREATE TABLE t1 (a int default 11, b int default 22, c int default (a+b+33));
To start simply: INSERT INTO t1 (a, b, c) VALUES (DEFAULT, DEFAULT, DEFAULT);
This gives us: SELECT * FROM t1;
+------+------+------+
| a | b | c |
+------+------+------+
| 11 | 22 | 66 |
+------+------+------+
No surprises. DELETE FROM t1;
INSERT INTO t1 (a, b, c) VALUES (44, 55, DEFAULT);
SELECT * FROM t1;
+------+------+------+
| a | b | c |
+------+------+------+
| 44 | 55 | 132 |
+------+------+------+
Again, no surprises. Now, let's reorder things a bit: DELETE FROM t1;
INSERT INTO t1 (b, c, a) VALUES (87, DEFAULT, 65);
Knowing that we're evaluating this left-to-right, and `a`, `b` and `c` start out set to their default values as defined in the table schema, what do we expect? <a=65, b=87, c=??> SELECT * FROM t1;
+------+------+------+
| a | b | c |
+------+------+------+
| 65 | 87 | 131 |
+------+------+------+
And, sure enough, there it is. > We respect your personal privacy
>
> We and our third party partners use cookies and other tracking technologies to provide a proactive support experience, enhance site navigation, analyze site usage, and assist in our marketing efforts.
>
> Learn more
And, "Learn more" is linked to https://calendly.com/privacy - so, yes, but it may be possible that by that point you're already being tracked. > Information Collected Automatically From You.
>
> [...]
>
> Third-Party Tools.
> We may disclose information to third parties or allow third parties to directly collect information using these technologies on our Website, such as social media companies, advertising networks, companies that provide analytics including ad tracking and reporting, security providers, and others that help us operate our business and Website. We use such third-party tools subject to your consent, opt-out preferences, or other appropriate legal basis where legally required. [...]
So, yeah, if you use Calendly, you accept their terms of use and their privacy policy has informed users of such third-party collection of data, so there's the informed consent by accepting these terms.
Temporary workaround is to set your computer's clock back to before the certificate expires, until a new client build is released with an updated certificate, presumably.
Surprisingly, not a DNS issue, for a change.