chias

IIRC they were part of a base64 encoded blob. IIRC base64 decoding was also referred to as an "advanced hacking technique". But your point very much stands.

Note: I work at LiteLLM

There exists a critical vulnerability which affects only Enterprise LiteLLM deployments, and does not affect OSS deployments.

We have provided our customers with patched releases distributed via a private registry and are allowing them some time to update their deployments before we release the fix in our public registry and disclose the vulnerability details. Releasing the fix publicly in an open source product would be a de-facto vulnerability disclosure.

Note: I work at LiteLLM

There exists a critical vulnerability which affects only Enterprise LiteLLM deployments, and does not affect OSS deployments.

We have provided our customers with patched releases distributed via a private registry and are allowing them some time to update their deployments before we release the fix in our public registry and disclose the vulnerability details. Releasing the fix publicly in an open source product would be a de-facto vulnerability disclosure.

The cookie banners are not required to be this way. They are deliberately designed to be as annoying as they can legally be (many actually moreso), in part to influence your perspective against GDPR.

Yes. I think the idea is that on the path of events or actions between the starting point and the target, you have already completed every single one, and all that remains now is the final step before you can call it done.

You've walked all but the last step of the journey.

What an excellent choice of product name :D

"You're da C"

if you're using firefox, you can generally juts ctrl-click on the page. It'll draw outlines around every child element without reflowing.

Generally, no.

Ignoring for now how you are synchronizing the database and filesystem, and how doing so may well result in your duplicate experiencing the same failure as the original, you can maybe recover from a small class of availability issues that could knock you out of an SLA.

But that assumes you can get online and can fully orchestrate the transition within less than 53 minutes of it starting. Including the time you took to become aware of it. And including the time to diagnose and decide that a switchover would resolve the problem. Including the time it takes for DNS caches to expire and point to the new host. Including the DNS caches which may ignore your TTL. And including all these things again when you switch back.

And assuming, of course, that it doesn't happen again for a whole year.

Perhaps to you. But that's because you have prior cultural knowledge of chess, and what it means to "play" something. It seems to me to be perfectly reasonable for an ai agent to define "play chess" as "behave in a way that this arbiter indicates that you have done well"

> I agree that it would be the right thing to do. Which is why you have to make the best attempt to make it the legal thing

Do you believe that in an ideal world, any instance of not "doing the right thing" should be illegal?

The url was to transfer log data from metabase to framework. It is not something that is intended for end user access.

The author mentions this in the second paragraph...