remram

Me? None. I'm not the one proposing the use of Rust and WASM for form validation.

What kind of validation are you going to do without a regular expression?

But the example code doesn't do much validation. If you did want to use a regex, you would have to compile and bundle the regex crate...

I don't use tmux.

CVE-2020-27347 is exactly the kind of memory safety bug exploitable by terminal output that I was talking about.

At least the article is honest about being a clickbaity AI-generated attack...

It "feels" much easier to generate random non-solutions and check if the random questions happen to pass, though. Is it really all there is to it? You increase the number of questions to compensate and that's the whole scheme? Wouldn't the responses be a ludicrous amount of data?

That's only for interactive proofs though. Like GP I have no problem understanding those.

You forget that tmux is a terminal emulator. Trusted programs can have untrusted/attacker-controlled terminal output. If the program running inside tmux (e.g. cat, curl -s, weechat) can output malformed unicode or escape commands that trigger crashes or code execution, it is actually a huge problem.

The verdicts:

> Thomas François, 52, a former Ubisoft editorial vice-president, was found guilty of sexual harassment.

> Serge Hascoët, 59, Ubisoft’s former chief creative officer and second-in-command, was found guilty of psychological harassment and complicity in sexual harassment.

> The former Ubisoft game director, Guillaume Patrux, 41, was found guilty of psychological harassment

How much does this particular slap reduce earnings really? Alphabet shows $41 billion before tax, so 0.7%? Assuming they do pay that amount. I'm not well-versed in financial matters so please check my numbers.

http://abc.xyz/investor/

It can't be shared without networking so I am not sure what you mean. Are you sure you need it to be shared?

Do you have any evidence at all of Mozilla doing anything? The facts are he resigned as CEO after visible external pressure.

As an outsider, it seems weird to me that you would go to Edge when you are unsatisfied by Mozilla's spotty long-term support. Edge exists because Microsoft dropped support for IE (and then for their own rendering engine altogether when they switched to Chromium). It seems to me that they have a strictly worse track record in the aspect you care about.

Or maybe I am wrong about the facts? I never used Edge.

See also SVCB

I thought this was possible to do with CEL but it looks like this has barely reached alpha: https://kubernetes.io/docs/reference/access-authn-authz/muta...

Webhooks like yours will still be needed for a while (or programmable frameworks like Kyverno).

I wonder if you can build this into your container runtime config instead. Automatically rewriting is nice but you will still see the rewritten image when reading from the API server.

Not to be confused with Kubernetes' Spiegel: https://spegel.dev/ https://github.com/spegel-org/spegel

Works for me (from France)

"?" call "into()" automatically, which covers simple wrapping.

The author dismissed that option saying "I value that docker build can have a clean environment every time", so this is self-inflicted.

It was written by one vendor for their own use. It is miles away from an RFC or "standard"

In my environment, the number one reason Apptainer is used has nothing to do with deployment, isolation, or software availability: it is to work around inode limits.

On our HPC cluster, each user has a quota of inodes on the shared filesystem. This makes installing some software with lots of files problematic (like Anaconda). An Apptainer image is a single file on the filesystem though (basically squashfs) so you can have those with as many files as you want in each.

Installing the same software normally is easy and works fine though, you just exchaust your quota.

That one does look like a bug. I stand corrected.

> Any ip like 2001:0000:0000::1 is going to be incorrect.

This is neither a possible input nor a possible output of that code.

No, on the contrary. You can't get a valid certificate for non-global IP, but you can already get a certificate for a domain name and point it to 192.168.0.1.

You can point a name at your home IP just as easily as any other IP.

So what do we call it? PNG3? The spec is titled "Portable Network Graphics Specification (Third Edition)".

Surely they aren't releasing a new, incompatible version and expecting us to pretend it's the same format...?

> This updates the existing image/png Internet Media type

whyyyyyyy

> `uv lock` fails if your lock file has a mismatch

Now you seem even more confused. Do you mean `uv sync` will fail? `uv lock` is literally the command you run when there's a mismatch between pyproject.toml and uv.lock to update uv.lock. That's why it's called lock.

Here's a full reproducer: https://gist.github.com/remram44/21c98db9a80213b2a3a5cce959d...

Check out branch "previous-blog". Run `docker build . -t uvtest`. You will see that it builds with no error, and if you run `docker run uvtest cat /app/uv.lock`, you will see that the uv.lock in the image is NOT the one in the repo. It has been updated silently, which is what gchamonlive and myself pointed out.

Now check out branch "master". Run `docker build . -t uvtest` again. You will see `error: The lockfile at `uv.lock` needs to be updated` which is what you say always happened.

That's surprising to me, it was when I used Comcast (2016) that I first purchased a cable modem. It did save me money.

> The parent's description isn't what happens with the original code

Yes, it is: both gchamonlive and myself pointed out that if your lock file exists and is out of date, your (previous) script would silently update it before installing. This would happen because `uv lock --check` would return false, triggering the call to `uv lock`.

Your new version no longer does that, because you removed `! uv lock --check` from the condition.

I see you just changed your article from what it was when we commented:

  if ! test -f uv.lock || ! uv lock --check 2>/dev/null; then uv lock; fi

Your new version no longer has the bug we are talking about. I don't know why you are trying to pretend it was never there though?